Closed Bug 1131720 Opened 7 years ago Closed 7 years ago

Intermittent run-by-dir test_whitespace.html | Different amount of expected children of ['div@id="container1" node', address: [object HTMLDivElement], role: section, address: [xpconnect wrapped nsIAccessible]]. - got 6, expected 5

Categories

(Core :: Disability Access APIs, defect)

x86_64
Windows 8.1
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: RyanVM, Unassigned)

References

Details

(Keywords: intermittent-failure)

08:19:59 INFO - 1369 INFO TEST-START | chrome://mochitests/content/a11y/accessible/tests/mochitest/treeupdate/test_whitespace.html
08:20:00 INFO - 1370 INFO must wait for load
08:20:00 INFO - 1371 INFO Invoke the 'remove middle img' test { scenario #0: expected 'hide' event; expected 'hide' event; expected 'reorder' event; }
08:20:00 INFO - 1372 INFO TEST-PASS | chrome://mochitests/content/a11y/accessible/tests/mochitest/treeupdate/test_whitespace.html | Wrong value of property 'role' for ['div@id="container1" node', address: [object HTMLDivElement], role: section, address: [xpconnect wrapped nsIAccessible]].
08:20:00 INFO - 1373 INFO TEST-UNEXPECTED-FAIL | chrome://mochitests/content/a11y/accessible/tests/mochitest/treeupdate/test_whitespace.html | Different amount of expected children of ['div@id="container1" node', address: [object HTMLDivElement], role: section, address: [xpconnect wrapped nsIAccessible]]. - got 6, expected 5
08:20:00 INFO - 1374 INFO TEST-PASS | chrome://mochitests/content/a11y/accessible/tests/mochitest/treeupdate/test_whitespace.html | Wrong value of property 'role' for ['div@id="container1" node', address: [object HTMLDivElement], role: section, address: [xpconnect wrapped nsIAccessible]].
08:20:00 INFO - 1375 INFO TEST-UNEXPECTED-FAIL | chrome://mochitests/content/a11y/accessible/tests/mochitest/treeupdate/test_whitespace.html | Different amount of expected children of ['div@id="container1" node', address: [object HTMLDivElement], role: section, address: [xpconnect wrapped nsIAccessible]]. - got 4, expected 3
08:20:00 INFO - 1376 INFO TEST-PASS | chrome://mochitests/content/a11y/accessible/tests/mochitest/treeupdate/test_whitespace.html | Test with ID = 'remove middle img' succeed. Event hide was handled.
08:20:00 INFO - 1377 INFO TEST-PASS | chrome://mochitests/content/a11y/accessible/tests/mochitest/treeupdate/test_whitespace.html | Test with ID = 'remove middle img' succeed. Event hide was handled.
08:20:00 INFO - 1378 INFO TEST-PASS | chrome://mochitests/content/a11y/accessible/tests/mochitest/treeupdate/test_whitespace.html | Test with ID = 'remove middle img' succeed. Event reorder was handled.
I continue to be able to reproduce this error on try:
https://treeherder.mozilla.org/#/jobs?repo=try&revision=98fd5e44a30e&filter-searchStr=osx

This is something which I don't know anything about debugging or even fiddling with.  What is happening is that we are running each accessibility directory as a standalone directory (fresh browser launch with a fresh profile, then after the tests in only that directory run shut down the directory).

This usually affects timing (for example this test case is the last to run in a nice healthy list of tests) either while depending on the browser to startup, or if we shutdown to fast.  I doubt this is shutdown or startup related though.  Other issues are around GC's (timing is much different for the whole session), or sometimes previous test cases affecting the browser.

David, can you help find someone to help us hack this a bit or look into what is really going on?  Even a few suggestions to try out would be helpful!
Flags: needinfo?(dbolter)
Alex might have ideas.
Flags: needinfo?(dbolter) → needinfo?(surkov.alexander)
It will be helpful to know what the extra accessible is. It'd be nice if testAccessilbeTree logged the difference (http://mxr.mozilla.org/mozilla-central/source/accessible/tests/mochitest/common.js#454).
Flags: needinfo?(surkov.alexander)
I haven't seen this after adding more verbose information to common.js, going to close as wontfix.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.