Bug 37005 - REGRESSION(56930): platform/mac/accessibility/aria-liveregions-notifications.html timed out on Leopard Bot
Summary: REGRESSION(56930): platform/mac/accessibility/aria-liveregions-notifications....
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nobody
Depends on: 31680
  Show dependency treegraph
Reported: 2010-04-01 21:01 PDT by Eric Seidel (no email)
Modified: 2010-04-06 19:30 PDT (History)
5 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Eric Seidel (no email) 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

I'm starting to wonder if DRT just has random timeout problems.
Comment 1 Eric Seidel (no email) 2010-04-01 21:04:59 PDT
This may have just been a regression from http://trac.webkit.org/changeset/56962.
Comment 2 Adam Barth 2010-04-01 21:29:57 PDT
My money is on http://build.webkit.org/changes/7752
Comment 3 Kent Tamura 2010-04-01 21:30:57 PDT
According to the buildbot, aria-liveregions-notifications.html failed at r56931-r56932, r56934-r56946, r56052-r56954.
Comment 4 Eric Seidel (no email) 2010-04-01 21:32:06 PDT
Meaning http://trac.webkit.org/changeset/56930 from bug 36977.
Comment 5 Adam Barth 2010-04-01 21:41:42 PDT
Tentatively marking as fixed.
Comment 6 chris fleizach 2010-04-01 21:42:24 PDT
whatever happened to giving the person who made a commit a chance to fix.
Comment 7 Adam Barth 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.