686741 - Something is fishy with android tests timing out

Status: RESOLVED DUPLICATE of bug 675297

(Release Engineering :: General, defect, P3)

Description

[Josh Matthews [:jdm]]

From a log that I was just sent:

command timed out: 2400 seconds without output
program finished with exit code 1
elapsedTime=172329.056456
TinderboxPrint: crashtest<br/><em class="testfail">T-FAIL</em>
buildbot.slave.commands.TimeoutError: command timed out: 2400 seconds without output
TinderboxPrint: crashtest<br/><em class="testfail">timeout</em>
======== Finished 'python reftest/remotereftest.py ...' warnings (results: 1, elapsed: 47 hrs, 52 mins, 9 secs) ========

It looks like it timed out like usual, but then decided to just wait for 47 hours? That doesn't look right to me at all.

Comment 1

[Chris Cooper [:coop] (he/him)]

Josh: do you have a link to that log? I'd like to have a closer look.

Comment 2

[Josh Matthews [:jdm]]

http://ftp.mozilla.org/pub/mozilla.org/mobile/try-builds/[e-mail]-aa3f195cd4cb/try-android-debug/try_tegra_android-debug_test-crashtest-build322.txt.gz

Comment 3

[Phil Ringnalda (:philor)]

That's a bug 686378, but before the bug 650535 patch turned it from a "okay, unhandled exception failing to even get the browser going, fine, 2400 second timeout, whatever, I'm just going to sit here until either bear reboots me, or the power goes out in the colo, or someone trips and knocks over my rack" into just a "no process, no cry, 43 seconds and I'm out of here with an exit code 1."

Comment 4

[Mike Taylor [:bear]]

this looks to be bug 675297