This started in the last few hours, somewhere in this range: https://tbpl.mozilla.org/?tree=Mozilla-Inbound&jobname=Ubuntu VM 12.04 mozilla-inbound debug test jetpack&tochange=6809ce23f0fe&fromchange=a4e77cc8f619 Outputting "unknown" as a test name is not ideal, since TBPL hits all sorts of false positives when searching for intermittent bugs containing that in the summary. Ubuntu VM 12.04 mozilla-inbound debug test jetpack on 2014-06-04 08:15:26 PDT for push d37aa03d00fb slave: tst-linux32-spot-360 https://tbpl.mozilla.org/php/getParsedLog.php?id=41035309&tree=Mozilla-Inbound { Running tests on Firefox 32.0a1/Gecko 32.0a1 ({ec8030f7-c20a-464f-9b0e-13a3a9e97384}) under linux/x86. --DOMWINDOW == 14 (0x9ec6dc00) [pid = 1486] [serial = 14] [outer = 0x9ec6d800] [url = about:blank] --DOMWINDOW == 13 (0xa3b39270) [pid = 1486] [serial = 9] [outer = 0xa3b388c0] [url = about:blank] --DOMWINDOW == 12 (0xa7b12400) [pid = 1486] [serial = 2] [outer = 0xaaf8f800] [url = about:blank] Program firefox/firefox-bin (pid = 1486) received signal 11. Stack: UNKNOWN [/builds/slave/test/build/firefox/libxul.so +0x027DA772] UNKNOWN 0xb779840c UNKNOWN [/builds/slave/test/build/firefox/libxul.so +0x023CB680] UNKNOWN [/builds/slave/test/build/firefox/libxul.so +0x024E16A3] UNKNOWN [/builds/slave/test/build/firefox/libxul.so +0x024E184A] UNKNOWN [/builds/slave/test/build/firefox/libxul.so +0x024E2E35] UNKNOWN [/builds/slave/test/build/firefox/libxul.so +0x024E327C] UNKNOWN [/builds/slave/test/build/firefox/libxul.so +0x024E3331] UNKNOWN [/builds/slave/test/build/firefox/libxul.so +0x024EDE35] UNKNOWN [/builds/slave/test/build/firefox/libxul.so +0x024EE00B] UNKNOWN [/builds/slave/test/build/firefox/libxul.so +0x024EE196] UNKNOWN [/builds/slave/test/build/firefox/libxul.so +0x021DEB31] UNKNOWN 0xac5f3d71 UNKNOWN 0x9ee40048 Sleeping for 300 seconds. Type 'gdb firefox/firefox-bin 1486' to attach your debugger to this thread. Done sleeping... TEST-UNEXPECTED-FAIL | unknown | Test output exceeded timeout (300s). Traceback (most recent call last): File "jetpack/bin/cfx", line 33, in <module> cuddlefish.run() File "/builds/slave/test/build/jetpack/python-lib/cuddlefish/__init__.py", line 606, in run test_all_packages(env_root, defaults=options.__dict__) File "/builds/slave/test/build/jetpack/python-lib/cuddlefish/__init__.py", line 492, in test_all_packages env_root=env_root) File "/builds/slave/test/build/jetpack/python-lib/cuddlefish/__init__.py", line 928, in run enable_e10s=enable_e10s) File "/builds/slave/test/build/jetpack/python-lib/cuddlefish/runner.py", line 751, in run_app OUTPUT_TIMEOUT, test_name, parseable) Exception: Test output exceeded timeout (300s). program finished with exit code 1 elapsedTime=608.666636 TinderboxPrint:testpkgs<br/>0/0 Unknown Error: command finished with exit code: 1 ========= Finished 'python jetpack/bin/cfx ...' warnings (results: 1, elapsed: 10 mins, 25 secs) (at 2014-06-04 08:29:15.284357) ========= }

(In reply to Ed Morley [:edmorley UTC+0] from comment #0) > This started in the last few hours, somewhere in this range: > https://tbpl.mozilla.org/?tree=Mozilla-Inbound&jobname=Ubuntu VM 12.04 > mozilla-inbound debug test > jetpack&tochange=6809ce23f0fe&fromchange=a4e77cc8f619 > > Outputting "unknown" as a test name is not ideal, since TBPL hits all sorts > of false positives when searching for intermittent bugs containing that in > the summary. What is ideal here then? It looks like `unknown` is used only if there is a 300s time period without any changes to the log file, so the failure that you linked to in this bug failed before any tests started. SO it seems to me that using `unknown` in that case was alright.

(In reply to Erik Vold [:erikvold] [:ztatic] from comment #1) > What is ideal here then? It looks like `unknown` is used only if there is a > 300s time period without any changes to the log file, so the failure that > you linked to in this bug failed before any tests started. SO it seems to > me that using `unknown` in that case was alright. Mochitest does things like: http://mxr.mozilla.org/mozilla-central/source/testing/mochitest/runtests.py#189 TEST-UNEXPECTED-FAIL | runtests.py | Timed out while waiting for server startup. Though I never really like using "runtests.py", so maybe something like: TEST-UNEXPECTED-FAIL | Jetpack startup | Timed out while waiting for foo.

(In reply to Ed Morley [:edmorley UTC+0] from comment #2) > (In reply to Erik Vold [:erikvold] [:ztatic] from comment #1) > > What is ideal here then? It looks like `unknown` is used only if there is a > > 300s time period without any changes to the log file, so the failure that > > you linked to in this bug failed before any tests started. SO it seems to > > me that using `unknown` in that case was alright. > > Mochitest does things like: > http://mxr.mozilla.org/mozilla-central/source/testing/mochitest/runtests. > py#189 > TEST-UNEXPECTED-FAIL | runtests.py | Timed out while waiting for server > startup. > > Though I never really like using "runtests.py", so maybe something like: > TEST-UNEXPECTED-FAIL | Jetpack startup | Timed out while waiting for foo. Alright, that'll be easy.

Commits pushed to master at https://github.com/mozilla/addon-sdk https://github.com/mozilla/addon-sdk/commit/33699d786a07b54716aaa6dd7cf60cf610fd1636 Bug 1020463 use "Jetpack startup" instead on "unknown" in TBPL output when the test suite fails to start https://github.com/mozilla/addon-sdk/commit/048ce315a005b58b3fd1b87b6b5fe3ca1042bf8d Merge pull request #1508 from erikvold/1020463 Bug 1020463 use "Jetpack startup" instead on "unknown" in TBPL output when the test suite fails to start r=@jsantell

Is this fixed now?

(In reply to Dave Townsend [:mossop] from comment #6) > Is this fixed now? I was only waiting for an uplift to aurora in bug 1026636 before closing this one.