Summary: | http/tests/incremental/split-hex-entities.pl timed out on Gtk Linux 32-bit Debug Bot | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Eric Seidel (no email) <eric> | ||||
Component: | Tools / Tests | Assignee: | Eric Seidel (no email) <eric> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | commit-queue, gustavo, mrobinson, ossy, svillar, xan.lopez | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | PC | ||||||
OS: | OS X 10.5 | ||||||
Bug Depends on: | |||||||
Bug Blocks: | 33295 | ||||||
Attachments: |
|
Description
Eric Seidel (no email)
2010-01-09 19:47:18 PST
It occured again on GTK Linux 64-bit Debug http://build.webkit.org/results/GTK%20Linux%2064-bit%20Debug/r53182%20%282349%29/results.html Timed out again: http://build.webkit.org/results/GTK%20Linux%2032-bit%20Debug/r53790%20(2643)/results.html I suspect this could be a real timeout. It would help greatly if someone with a gtk build could time how long this test takes, or get a sample of what it's doing. If we don't make any progress soon, we should skip this to keep the bots green until we have a test expectations system which allows us to have tests which expect both pass and timeout results. Created attachment 47456 [details]
Patch
Comment on attachment 47456 [details] Patch Rejecting patch 47456 from commit-queue. Failed to run "['/Users/eseidel/Projects/CommitQueue/WebKitTools/Scripts/svn-apply', '--reviewer', 'Gustavo Noronha Silva', '--force']" exit_code: 1 patching file LayoutTests/ChangeLog Hunk #1 succeeded at 1 with fuzz 3. patching file LayoutTests/platform/gtk/Skipped Hunk #1 FAILED at 5781. 1 out of 1 hunk FAILED -- saving rejects to file LayoutTests/platform/gtk/Skipped.rej Full output: http://webkit-commit-queue.appspot.com/results/216109 Attachment 47456 [details] was posted by a committer and has review+, assigning to Eric Seidel for commit.
Committed r54254: <http://trac.webkit.org/changeset/54254> I ran this a few times locally and it seems to be a very slow test: 5.20s total testing time 7.63s total testing time 7.73s total testing time Meanwhile another test shows: 2.25s total testing time 2.23s total testing time (so we know it isn't all overhead) Our debug bots should be faster now, so maybe we can unskip this, at least. |