Open Bug 386910 Opened 17 years ago Updated 2 years ago

scriptaculous test fails when running slowly

Categories

(Core :: DOM: Core & HTML, defect, P5)

defect

Tracking

()

People

(Reporter: dbaron, Unassigned)

References

Details

The scriptaculous test, dom/tests/mochitest/ajax/scriptaculous/test_Scriptaculous.html , seems to fail when running slowly.  It failed once on the tinderbox earlier today, and I reproduced the failure running it under valgrind (thinking that that might show a reason for random failure).  Valgrind didn't show any warnings, but the test failed in exactly the same way, which suggests to me that there's something timing-dependent in the test that fails when the test is run slowly.  The failures that showed on both the tinderbox and for me are:

not ok - testInPlaceEditor 31 assertions, 2 failures, 0 errors Failure:
assertEqual: expected "'Server received: To be edited'", actual "'Saving...'"
Failure: assert: got "false"
not ok - testInPlaceEditor 31 assertions, 2 failures, 0 errors Failure:
assertEqual: expected "'Server received: To be edited'", actual "'Saving...'"
Failure: assert: got "false"
not ok - testHovering 1 assertions, 1 failures, 0 errors Failure: should be
transparent after mouse leaves element: expected "'transparent'", actual
"'rgb(255, 255, 175)'"
ok - testLoadsTextFromServer
not ok - testLoadsTextFromServer 3 assertions, 2 failures, 0 errors Failure:
assertEqual: expected "'Text from server'", actual "'Loading...'" Failure:
assert: got "false"
not ok - testLoadsTextFromServer 3 assertions, 2 failures, 0 errors Failure:
assertEqual: expected "'Text from server'", actual "'Loading...'" Failure:
assert: got "false"

I also saw an additional failure at the very end that the tinderbox didn't:

ok - testElementCollectTextNodes
ok - testElementCollectTextNodes
ok - testElementCollectTextNodes
not ok - testElementCollectTextNodes

(I just ran the tests using valgrind --tool=memcheck --leak-check=no --trace-children=yes --num-callers=500 perl ./runtests.pl and then clicked on the test I wanted to run.)
These tests are still failing intermittently on Tinderbox, see:
https://wiki.mozilla.org/Tinderbox/Nov-2008-Orange-Compendium
Component: Testing → DOM
OS: Linux → All
QA Contact: testing → general
Hardware: x86 → All
I see similar failures when running on fennec on the Nokia device (I don't see any issues with fenneco n the desktop though):
39 ERROR TEST-UNEXPECTED-FAIL | /tests/dom/tests/mochitest/ajax/scriptaculous/test_Scriptaculous.html | testLoadsTextFromServer - 3 assertions, 2 failures, 0 errors
40 ERROR TEST-UNEXPECTED-FAIL | /tests/dom/tests/mochitest/ajax/scriptaculous/test_Scriptaculous.html | testLoadsTextFromServer - 3 assertions, 2 failures, 0 errors
597 ERROR TEST-UNEXPECTED-FAIL | /tests/dom/tests/mochitest/ajax/scriptaculous/test_Scriptaculous.html | testElementMorph - 6 assertions, 2 failures, 0 errors
598 ERROR TEST-UNEXPECTED-FAIL | /tests/dom/tests/mochitest/ajax/scriptaculous/test_Scriptaculous.html | testElementMorph - 6 assertions, 2 failures, 0 errors
635 ERROR TEST-UNEXPECTED-FAIL | /tests/dom/tests/mochitest/ajax/scriptaculous/test_Scriptaculous.html | testElementCollectTextNodes - 4 assertions, 1 failures, 0 errors
695 ERROR TEST-UNEXPECTED-FAIL | /tests/dom/tests/mochitest/ajax/scriptaculous/test_Scriptaculous.html | Test timed out.


Oddly enough, I think these pass on the maemo device when run outside of the mochitest framework.  We might need to look there as a starting point.
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.
Priority: -- → P5
Component: DOM → DOM: Core & HTML
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.