RESOLVED FIXED Bug 37005
REGRESSION(56930): platform/mac/accessibility/aria-liveregions-notifications.html timed out on Leopard Bot 
https://bugs.webkit.org/show_bug.cgi?id=37005
Summary REGRESSION(56930): platform/mac/accessibility/aria-liveregions-notifications....
Eric Seidel (no email)
Reported 2010-04-01 21:01:03 PDT
platform/mac/accessibility/aria-liveregions-notifications.html timed out on Leopard Bot --- /Volumes/Big/WebKit-BuildSlave/leopard-intel-release-tests/build/layout-test-results/platform/mac/accessibility/aria-liveregions-notifications-expected.txt 2010-04-01 20:29:30.000000000 -0700 +++ /Volumes/Big/WebKit-BuildSlave/leopard-intel-release-tests/build/layout-test-results/platform/mac/accessibility/aria-liveregions-notifications-actual.txt 2010-04-01 20:29:30.000000000 -0700 @@ -1,3 +1,4 @@ +FAIL: Timed out waiting for notifyDone to be called new text element This tests that ARIA live regions are sending out the correct notifications. We perform four operations (add, remove, change text, change alt tag), each one should trigger a live region notification http://trac.webkit.org/browser/trunk/LayoutTests/platform/mac/accessibility/aria-liveregions-notifications.html I'm starting to wonder if DRT just has random timeout problems.
Attachments
Add attachment proposed patch, testcase, etc.
Eric Seidel (no email)
Comment 1 2010-04-01 21:04:59 PDT
This may have just been a regression from http://trac.webkit.org/changeset/56962.
Adam Barth
Comment 2 2010-04-01 21:29:57 PDT
My money is on http://build.webkit.org/changes/7752
Kent Tamura
Comment 3 2010-04-01 21:30:57 PDT
According to the buildbot, aria-liveregions-notifications.html failed at r56931-r56932, r56934-r56946, r56052-r56954.
Eric Seidel (no email)
Comment 4 2010-04-01 21:32:06 PDT
Meaning http://trac.webkit.org/changeset/56930 from bug 36977.
Adam Barth
Comment 5 2010-04-01 21:41:42 PDT
Tentatively marking as fixed.
chris fleizach
Comment 6 2010-04-01 21:42:24 PDT
whatever happened to giving the person who made a commit a chance to fix.
Adam Barth
Comment 7 2010-04-01 21:45:20 PDT
The bustage has been in the tree for 9 hours and no one was around on IRC. Plus, it's a three line patch that easy to roll back in if we're wrong.
Note You need to log in before you can comment on or make changes to this bug.