Closed Bug 880619 Opened 11 years ago Closed 11 years ago

TEST-UNEXPECTED-FAIL | tests/test-dom.test on / emit | Test output exceeded timeout (60s).

Categories

(Add-on SDK Graveyard :: General, defect, P2)

All
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: KWierso, Unassigned)

References

()

Details

(Keywords: intermittent-failure)

This has happened fairly frequently in the last two pushes to the repository.

TEST-UNEXPECTED-FAIL | tests/test-dom.test on / emit | Test output exceeded timeout (60s).
Traceback (most recent call last):
  File "bin/cfx", line 33, in <module>
    cuddlefish.run()
  File "/builds/slave/test/addonsdk-poller/addon-sdk-496665ddc4f7/python-lib/cuddlefish/__init__.py", line 617, in run
    test_all(env_root, defaults=options.__dict__)
  File "/builds/slave/test/addonsdk-poller/addon-sdk-496665ddc4f7/python-lib/cuddlefish/__init__.py", line 397, in test_all
    test_all_packages(env_root, defaults)
  File "/builds/slave/test/addonsdk-poller/addon-sdk-496665ddc4f7/python-lib/cuddlefish/__init__.py", line 490, in test_all_packages
    env_root=env_root)
  File "/builds/slave/test/addonsdk-poller/addon-sdk-496665ddc4f7/python-lib/cuddlefish/__init__.py", line 937, in run
    pkgdir=options.pkgdir)
  File "/builds/slave/test/addonsdk-poller/addon-sdk-496665ddc4f7/python-lib/cuddlefish/runner.py", line 745, in run_app
    OUTPUT_TIMEOUT, test_name, parseable)
Exception: Test output exceeded timeout (60s).
TinderboxPrint:Jetpack<br/>229/0
I'm able to reproduce this locally every single time I've tried to run cfx testall today, using a Nightly built from http://hg.mozilla.org/mozilla-central/rev/efbe547a7972
I'm not sure why this is permanently timing out on my linux VM with the current Nightly build, but it's only intermittently failing on tbpl...

If I add a | console.log(window); | to that test, it logs "undefined" to the console.
And, just for fun, I commented out "test on / emit", and then "test once" started timing out identically...
Similarly, if I comment out "test on / emit" AND "test once", "test remove" times out.

If I comment out all of the tests in test-dom.js, the test suite progresses just fine.

Is anyone else able to reproduce this locally with the latest Nightly builds?
Commit pushed to integration at https://github.com/mozilla/addon-sdk

https://github.com/mozilla/addon-sdk/commit/559fec67084c38aed19f811200bd2f595cd0c912
Bug 880619 - Disable test-dom.js because of frequent test failures. r=mossop
Commit pushed to master at https://github.com/mozilla/addon-sdk

https://github.com/mozilla/addon-sdk/commit/559fec67084c38aed19f811200bd2f595cd0c912
Bug 880619 - Disable test-dom.js because of frequent test failures. r=mossop
And pushed to inbound: http://hg.mozilla.org/integration/mozilla-inbound/rev/264002f52216


Irakli, any chance you know why these would fail all of the sudden the way they are?
Flags: needinfo?(rFobic)
https://hg.mozilla.org/mozilla-central/rev/264002f52216
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Oops, forgot the [leave open]...
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Commit pushed to australis at https://github.com/mozilla/addon-sdk

https://github.com/mozilla/addon-sdk/commit/559fec67084c38aed19f811200bd2f595cd0c912
Bug 880619 - Disable test-dom.js because of frequent test failures. r=mossop
clear need info
Flags: needinfo?(rFobic)
Haven't seen this for a while, closing the bug.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.