Summary: | LayoutTests are too slow | ||
---|---|---|---|
Product: | WebKit | Reporter: | Eric Seidel (no email) <eric> |
Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED CONFIGURATION CHANGED | ||
Severity: | Normal | CC: | ahmad.saleem792, ap |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | PC | ||
OS: | OS X 10.5 | ||
Bug Depends on: | 27998, 28008 | ||
Bug Blocks: | |||
Attachments: |
Description
Eric Seidel (no email)
2009-08-04 14:22:13 PDT
Created attachment 34085 [details]
Fix fast/events/click-count.html
Committing to http://svn.webkit.org/repository/webkit/trunk ... M LayoutTests/ChangeLog M LayoutTests/fast/events/click-count.html Committed r46779 M LayoutTests/ChangeLog M LayoutTests/fast/events/click-count.html r46779 = e94d8b69e0213dc93223db07ffb9f9f66204ff85 (trunk) No changes between current HEAD and refs/remotes/trunk Resetting to the latest refs/remotes/trunk http://trac.webkit.org/changeset/46779 Is this bug going to be used for investigating which tests are slow or for fixing individual tests? If the latter, it's fast going to get confusing with multiple patches. I'd suggest that you spin off separate bugs for tests that you're fixing rather than attaching them here. Created attachment 34105 [details]
slowest 1000 tests (Debug build on a Mac Pro)
Comment on attachment 34085 [details]
Fix fast/events/click-count.html
@bdash: agreed. I'll make this a meta bug.
This bug only serves a temporary purpose. It can be closed when most of the dependent bugs are closed. Created attachment 34108 [details]
slowest 1000 tests (Release build on a Mac Pro)
I sped up http/tests/misc/DOMContentLoaded-event.html and http/tests/navigation/multiple-back-forward-entries.html dramatically in r46808. Created attachment 34573 [details] r47037, slowest 1000 tests (Release build on a Mac Pro) The commit-queue seems zippier to run these days. I think we're making progress here! 346.82s total testing time is my current LayoutTest time for a release build. @ap - Do we need to track this old data anymore? I think we have now better metrics and machines and other improvement since 2009 that we can do better. I am marking this as "RESOLVED CONFIGURATION CHANGED" (because two patches / commit landed from this) but if you think it is something still worth tracking, please share your input. Thanks! |