Closed Bug 626647 Opened 14 years ago Closed 11 years ago

[BE CAREFUL: NOT states/test_link.html] Intermittent actions/test_link.html | Test timed out., test_tree.xul | nsIAccessibleEvent is not defined, test_treegrid.xul | Test timed out., test_obj.html | Test timed out., test_obj_css.html | Test timed out.

Categories

(Core :: Disability Access APIs, defect)

Product:
Core
Component:
Disability Access APIs
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: philor, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: intermittent-failure, Whiteboard: [test which aborts the suite])

Attachments

(1 file)

enable debug info
(deleted), patch
davidb
: review+
Details | Diff | Splinter Review
Probably all just fallout from the first timeout, though. http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1295355199.1295357725.13209.gz Rev3 WINNT 5.1 mozilla-central opt test mochitest-other on 2011/01/18 04:53:19 s: talos-r3-xp-015 http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1295358593.1295361081.30713.gz Rev3 WINNT 5.1 mozilla-central opt test mochitest-other on 2011/01/18 05:49:53 s: talos-r3-xp-043 228 INFO TEST-PASS | chrome://mochitests/content/a11y/accessible/actions/test_link.html | Wrong action name of the accessible for 'link1' - "jump" should equal "jump" 229 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/a11y/accessible/actions/test_link.html | Test timed out. 238 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/a11y/accessible/actions/test_tree.xul | [SimpleTest/SimpleTest.js, window.onerror] An error occurred - uncaught exception: [accessible/events.js, gA11yEventObserver.observe] This is expected if a previous test has been aborted... Initial exception was: [ ReferenceError: nsIAccessibleEvent is not defined ] at :0 247 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/a11y/accessible/actions/test_treegrid.xul | Test timed out. 256 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/a11y/accessible/attributes/test_obj.html | Test timed out. 265 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/a11y/accessible/attributes/test_obj_css.html | Test timed out. 266 ERROR TEST-UNEXPECTED-FAIL | (SimpleTest/TestRunner.js) | 4 test timeouts, giving up. 267 ERROR TEST-UNEXPECTED-FAIL | (SimpleTest/TestRunner.js) | Skipping 144 remaining tests.
enable debug info on test_link.html test - http://hg.mozilla.org/mozilla-central/rev/97863fd07535
I've backed out debug info enabling because of failure: 227 ERROR TEST-UNEXPECTED-FAIL | chrome://mochitests/content/a11y/accessible/actions/test_link.html | [SimpleTest/SimpleTest.js, window.onerror] An error occurred - invoker.getID is not a function at chrome://mochitests/content/a11y/accessible/events.js:280 http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1295369712.1295370774.8964.gz&fulltext=1 http://hg.mozilla.org/mozilla-central/rev/a1aacf3854ea fix is coming
Attached patch enable debug info (deleted) — — Splinter Review
Attachment #504767 - Flags: review?(bolterbugz)
Attachment #504767 - Flags: review?(bolterbugz) → review+
document load event is missed for the _blank document when the img1 of link1 is clicked (second test). When the link1 is clicked then document load event is delivered (first test).
Alexander, any ideas from the debug info?
(In reply to comment #37) > Alexander, any ideas from the debug info? nothing else than comment #10
(In reply to comment #10) > document load event is missed for the _blank document when the img1 of link1 is > clicked (second test). When the link1 is clicked then document load event is > delivered (first test). I'm not 100% clear on this. Is this just timing fragility in the tests? How about we comment out the fragile tests and file a bug?
(In reply to comment #39) > I'm not 100% clear on this. Is this just timing fragility in the tests? The test doesn't look guilty. > How > about we comment out the fragile tests and file a bug? I've never seen it on try server builds for bug 606924. Perhaps it makes sense to wait for a landing to check if it really helps.
(In reply to comment #40) > I've never seen it on try server builds for bug 606924. Perhaps it makes sense > to wait for a landing to check if it really helps. Yep.
Summary: Intermittent test_link.html | Test timed out., test_tree.xul | nsIAccessibleEvent is not defined, test_treegrid.xul | Test timed out., test_obj.html | Test timed out., test_obj_css.html | Test timed out. → Intermittent actions/test_link.html | Test timed out., test_tree.xul | nsIAccessibleEvent is not defined, test_treegrid.xul | Test timed out., test_obj.html | Test timed out., test_obj_css.html | Test timed out.
Summary: Intermittent actions/test_link.html | Test timed out., test_tree.xul | nsIAccessibleEvent is not defined, test_treegrid.xul | Test timed out., test_obj.html | Test timed out., test_obj_css.html | Test timed out. → Intermittent actions/test_link.html [BE CAREFUL: not states/test_link.html] | Test timed out., test_tree.xul | nsIAccessibleEvent is not defined, test_treegrid.xul | Test timed out., test_obj.html | Test timed out., test_obj_css.html | Test timed out.
Summary: Intermittent actions/test_link.html [BE CAREFUL: not states/test_link.html] | Test timed out., test_tree.xul | nsIAccessibleEvent is not defined, test_treegrid.xul | Test timed out., test_obj.html | Test timed out., test_obj_css.html | Test timed out. → [BE CAREFUL: NOT states/test_link.html] Intermittent actions/test_link.html | Test timed out., test_tree.xul | nsIAccessibleEvent is not defined, test_treegrid.xul | Test timed out., test_obj.html | Test timed out., test_obj_css.html | Test timed out.
Whiteboard: [orange][test which aborts the suite] → [test which aborts the suite]
(OrangeWFM bugs not touched for 2 months)
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: