702373 - [birch] Native Fennec mochitests intermittently time out before starting | TimeoutError: command timed out: 2400 seconds without output

Status: RESOLVED WORKSFORME

(Firefox for Android Graveyard :: General, defect, P5)

Description

[Matt Brubeck (:mbrubeck)]

+++ This bug was initially created as a clone of Bug #701841 +++

Sometimes mochitests on the Native Fennec builds (birch branch) time out right after "runtests.py | Running tests: start".

https://tbpl.mozilla.org/php/getParsedLog.php?id=7387833&tree=Birch
Android Tegra 250 birch opt test mochitest-5 on 2011-11-14 08:58:06 PST for push 16ab009adcb0

========= Started 'python mochitest/runtestsremote.py ...' warnings (results: 1, elapsed: 40 mins, 17 secs) ==========
python mochitest/runtestsremote.py --deviceIP 10.250.49.30 --xre-path ../hostutils/xre --utility-path ../hostutils/bin --certificate-path certs --app org.mozilla.fennec --console-level INFO --http-port 30043 --ssl-port 31043 --pidfile /builds/tegra-043/test/../runtestsremote.pid --test-path dom/tests/mochitest/ajax/jquery
 in dir /builds/tegra-043/test/build/tests (timeout 2400 secs)
 watching logfiles {}
 argv: ['python', 'mochitest/runtestsremote.py', '--deviceIP', '10.250.49.30', '--xre-path', '../hostutils/xre', '--utility-path', '../hostutils/bin', '--certificate-path', 'certs', '--app', 'org.mozilla.fennec', '--console-level', 'INFO', '--http-port', '30043', '--ssl-port', '31043', '--pidfile', '/builds/tegra-043/test/../runtestsremote.pid', '--test-path', 'dom/tests/mochitest/ajax/jquery']
 environment:
  PATH=/opt/local/bin:/opt/local/sbin:/opt/local/Library/Frameworks/Python.framework/Versions/2.6/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
  PWD=/builds/tegra-043/test/build/tests
  SUT_IP=10.250.49.30
  SUT_NAME=tegra-043
  __CF_USER_TEXT_ENCODING=0x1F6:0:0
 closing stdin
 using PTY: False
unable to execute ADB: ensure Android SDK is installed and adb is in your $PATH
restarting as root failed
reconnecting socket
INFO | runtests.py | Installing extension at /builds/tegra-043/test/build/tests/mochitest/extensions/specialpowers to /tmp/tmpmeapGZ.
INFO | runtests.py | Installing extension at /builds/tegra-043/test/build/tests/mochitest/extensions/worker to /tmp/tmpmeapGZ.
INFO | runtests.py | Installing extension at /builds/tegra-043/test/build/tests/mochitest/extensions/workerbootstrap to /tmp/tmpmeapGZ.
pushing directory: /tmp/tmpmeapGZ to /mnt/sdcard/tests/profile
args: ['/builds/tegra-043/test/build/hostutils/bin/xpcshell', '-g', '/builds/tegra-043/test/build/hostutils/xre', '-v', '170', '-f', './httpd.js', '-e', "const _PROFILE_PATH = '/tmp/tmp04muMW';const _SERVER_PORT = '30043'; const _SERVER_ADDR ='10.250.48.202';", '-f', './server.js']
INFO | runtests.py | Server pid: 934
pushing directory: /tmp/tmpmeapGZ to /mnt/sdcard/tests/profile
INFO | runtests.py | Running tests: start.


command timed out: 2400 seconds without output, killing pid 906
process killed by signal 9
program finished with exit code -1
elapsedTime=2417.877952
TinderboxPrint: mochitest-plain_2<br/><em class="testfail">T-FAIL</em>
buildbot.slave.commands.TimeoutError: command timed out: 2400 seconds without output, killing pid 906
TinderboxPrint: mochitest-plain_2<br/><em class="testfail">timeout</em>
======== Finished 'python mochitest/runtestsremote.py ...' warnings (results: 1, elapsed: 40 mins, 17 secs) ========

Comment 1

[Matt Brubeck (:mbrubeck)]

https://tbpl.mozilla.org/php/getParsedLog.php?id=7436198&tree=Birch

Comment 2

[Matt Brubeck (:mbrubeck)]

https://tbpl.mozilla.org/php/getParsedLog.php?id=7558557&tree=Birch

Comment 3

[Matt Brubeck (:mbrubeck)]

https://tbpl.mozilla.org/php/getParsedLog.php?id=7665908&tree=Birch

Comment 4

[:Ms2ger (he/him; ⌚ UTC+1/+2)]

https://tbpl.mozilla.org/php/getParsedLog.php?id=8136538&tree=Firefox

Comment 5

[Ed Morley [:emorley]]

Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that:
* Haven't changed in > 6months
* Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb}
* Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive.

I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases).

Sorry for the spam! Filter on: #FFA500