Closed Bug 969618 Opened 10 years ago Closed 9 years ago

TEST-UNEXPECTED-FAIL | addon-sdk/tests/test-selection.test No Selection Exception

Categories

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

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: RyanVM, Unassigned)

References

Details

(Keywords: intermittent-failure)

https://tbpl.mozilla.org/php/getParsedLog.php?id=34307482&tree=Fx-Team

Rev4 MacOSX Snow Leopard 10.6 fx-team opt test jetpack on 2014-02-07 12:44:19 PST for push 6330fb0cb998
slave: talos-r4-snow-116

TEST-START | tests/test-selection.test No Selection Exception
TEST-UNEXPECTED-FAIL | tests/test-selection.test No Selection Exception | Test output exceeded timeout (300s).
Traceback (most recent call last):
  File "jetpack/bin/cfx", line 33, in <module>
    cuddlefish.run()
  File "/builds/slave/talos-slave/test/build/jetpack/python-lib/cuddlefish/__init__.py", line 603, in run
    test_all_packages(env_root, defaults=options.__dict__)
  File "/builds/slave/talos-slave/test/build/jetpack/python-lib/cuddlefish/__init__.py", line 485, in test_all_packages
    env_root=env_root)
  File "/builds/slave/talos-slave/test/build/jetpack/python-lib/cuddlefish/__init__.py", line 925, in run
    pkgdir=options.pkgdir)
  File "/builds/slave/talos-slave/test/build/jetpack/python-lib/cuddlefish/runner.py", line 742, in run_app
    OUTPUT_TIMEOUT, test_name, parseable)
Exception: Test output exceeded timeout (300s).
Priority: -- → P2
It's been over a month since the last failure.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Resolution: FIXED → WORKSFORME
Status: RESOLVED → REOPENED
OS: Mac OS X → All
Hardware: x86_64 → All
Resolution: WORKSFORME → ---
Summary: Intermittent tests/test-selection.test No Selection Exception | Test output exceeded timeout (300s). → TEST-UNEXPECTED-FAIL | addon-sdk/tests/test-selection.test No Selection Exception
Inactive; closing (see bug 1180138).
Status: REOPENED → RESOLVED
Closed: 10 years ago9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.