[Webkit-unassigned] [Bug 72189] New: accessibility/adjacent-continuations-cause-assertion-failure.html flaky on Chromium win release bot
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Nov 11 14:54:32 PST 2011
https://bugs.webkit.org/show_bug.cgi?id=72189
Summary: accessibility/adjacent-continuations-cause-assertion-f
ailure.html flaky on Chromium win release bot
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: Tools / Tests
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: ojan at chromium.org
CC: arv at chromium.org
This looks like a bug in the test harness. Not really sure how this would happen. Looking at the diff, something would have to be going wrong with js-test-pre. I don't really understand how it's possible though. The same call that prints "Make sure that a debug assert is not triggered when constructing the accessibility tree for this page." should print the missing lines.
It's also weird that it just recently got flaky on only the Chromium windows bot (http://test-results.appspot.com/dashboards/flakiness_dashboard.html#tests=accessibility%2Fadjacent-continuations-cause-assertion-failure.html).
My best guess is that there is some weird interaction between this test and some test that runs before it.
--- e:\b\build\slave\Webkit_Win\build\layout-test-results\accessibility/adjacent-continuations-cause-assertion-failure-expected.txt
+++ e:\b\build\slave\Webkit_Win\build\layout-test-results\accessibility/adjacent-continuations-cause-assertion-failure-actual.txt
@@ -3,10 +3,7 @@
z
End of test
Make sure that a debug assert is not triggered when constructing the accessibility tree for this page.
-
On success, you will see a series of "PASS" messages, followed by "TEST COMPLETE".
-
-
AXRole: AXWebArea AXValue:
AXRole: AXStaticText AXValue: x
AXRole: AXGroup AXValue:
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list