649829 - Looks like Tzoom is hanging on Android ("failed to initialize browser")

Status: RESOLVED FIXED

(Testing :: Talos, defect)

Description

[cmtalbert]

I'm not sure if this is filed yet, but I can't find any bugs.  Feel free to dupe.

It looks like tzoom is hanging the browser and failing to find the output file generated by talos.

Full log: http://tinderbox.mozilla.org/showlog.cgi?log=Mobile/1302725075.1302725812.11772.gz&fulltext=1

Relevant buildstep:
======== BuildStep started ========
'python remotePerfConfigurator.py ...'
=== Output ===
python remotePerfConfigurator.py -v -e org.mozilla.fennec -t tegra-086 -b 1.9.2 --branchName mobile --resultsServer graphs.mozilla.org --resultsLink /server/collect.cgi --activeTests tzoom --remoteDevice 10.250.49.74 --sampleConfig remote.config --output local.yml --webServer bm-remote.build.mozilla.org --browserWait 60
 in dir /builds/tegra-086/test/../talos-data/talos/ (timeout 1200 secs)
 watching logfiles {}
 argv: ['python', 'remotePerfConfigurator.py', '-v', '-e', 'org.mozilla.fennec', '-t', 'tegra-086', '-b', '1.9.2', '--branchName', 'mobile', '--resultsServer', 'graphs.mozilla.org', '--resultsLink', '/server/collect.cgi', '--activeTests', 'tzoom', '--remoteDevice', '10.250.49.74', '--sampleConfig', 'remote.config', '--output', 'local.yml', '--webServer', 'bm-remote.build.mozilla.org', '--browserWait', '60']
 environment:
  PATH=/opt/local/Library/Frameworks/Python.framework/Versions/2.6/bin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
  PWD=/builds/tegra-086/talos-data/talos
  SUT_IP=10.250.49.74
  SUT_NAME=tegra-086
  __CF_USER_TEXT_ENCODING=0x1F6:0:0
 closing stdin
 using PTY: False
reconnecting socket
Writing configuration:
 - exePath = org.mozilla.fennec
 - configPath = 
 - sampleConfig = remote.config
 - outputName = local.yml
 - title = tegra-086
 - branch = 1.9.2
 - branchName = mobile
 - buildid = 2011041312
 - currentDate = 20110413_1313
 - browserWait = 60
 - verbose = True
 - testDate = 
 - useId = False
 - resultsServer = graphs.mozilla.org
 - resultsLink = /server/collect.cgi
 - activeTests = tzoom
 - noChrome = False
 - fast = False
 - testPrefix = 
 - extension = 
 - masterIniSubpath = application.ini
 - test_timeout = 1200
 - symbolsPath = 
 - addonID = 
 - noShutdown = False
 - extraPrefs = []
 - remoteDevice = 10.250.49.74
 - remotePort = 20701
 - webServer = bm-remote.build.mozilla.org
 - deviceRoot = /mnt/sdcard/tests
program finished with exit code 0
elapsedTime=4.491969
=== Output ended ===
======== BuildStep ended ========
======== BuildStep started ========
'python run_tests.py ...' warnings
=== Output ===
python run_tests.py --noisy local.yml
 in dir /builds/tegra-086/test/../talos-data/talos/ (timeout 21600 secs)
 watching logfiles {}
 argv: ['python', 'run_tests.py', '--noisy', 'local.yml']
 environment:
  PATH=/opt/local/Library/Frameworks/Python.framework/Versions/2.6/bin:/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
  PWD=/builds/tegra-086/talos-data/talos
  SUT_IP=10.250.49.74
  SUT_NAME=tegra-086
  __CF_USER_TEXT_ENCODING=0x1F6:0:0
 closing stdin
 using PTY: False
reconnecting socket
RETURN:s: tegra-086
DeviceManager: error pulling file: No such file or directory
RETURN:id:20110413124147
RETURN:<a href = "http://hg.mozilla.org/mozilla-central/rev/4624580d88c0">rev:4624580d88c0</a>
tegra-086: 
		Started Wed, 13 Apr 2011 13:14:29
Running test tzoom: 
		Started Wed, 13 Apr 2011 13:14:29
reconnecting socket
FIRE PROC: ' "MOZ_CRASHREPORTER_SHUTDOWN=1,MOZ_CRASHREPORTER_NO_REPORT=1,NO_EM_RESTART=1" org.mozilla.fennec  -profile /mnt/sdcard/tests/profile http://bm-remote.build.mozilla.org/getInfo.html'
DeviceManager: error pulling file: No such file or directory
reconnecting socket
pushing directory: /tmp/tmp09hgT_/profile to /mnt/sdcard/tests/profile
NOISE: __startSecondTimestamp1302725715151__endSecondTimestamp
Failed tzoom: 
		Stopped Wed, 13 Apr 2011 13:15:16
FAIL: Busted: tzoom
FAIL: failed to initialize browser
Completed test tzoom: 
		Stopped Wed, 13 Apr 2011 13:15:16
RETURN: cycle time: 00:00:47<br>
tegra-086: 
		Stopped Wed, 13 Apr 2011 13:15:16
Sending results: 
		Started Wed, 13 Apr 2011 13:15:16
RETURN:<br>
RETURN:<p style="font-size:smaller;">Details:<br>|</p>
Completed sending results: 
		Stopped Wed, 13 Apr 2011 13:15:16
program finished with exit code 0
elapsedTime=50.095384
TinderboxPrint:s: tegra-086

TinderboxPrint:id:20110413124147

TinderboxPrint:<a href = "http://hg.mozilla.org/mozilla-central/rev/4624580d88c0">rev:4624580d88c0</a>

TinderboxPrint:FAIL: Busted: tzoom

TinderboxPrint:FAIL: failed to initialize browser

TinderboxPrint: cycle time: 00:00:47<br>

TinderboxPrint:<br>

TinderboxPrint:<p style="font-size:smaller;">Details:<br>|</p>
=== Output ended ===
======== BuildStep ended ========

Comment 1

[Aki Sasaki (not active)]

If you look at the mobile tinderbox front page, Tzoom is one of the greener suites.  This looks like an intermittent orange for whatever reason (code, infra, slave, other)

Comment 2

[Joel Maher ( :jmaher ) (UTC -8)]

actually in that log snippet we never pass getInfo.html, that is a sign that something else is wrong besides the test.

Comment 3

[Aki Sasaki (not active)]

(In reply to comment #1)
> If you look at the mobile tinderbox front page, Tzoom is one of the greener
> suites.  This looks like an intermittent orange for whatever reason (code,
> infra, slave, other)

(Now one of the least green suites. Yay progress)

Comment 5

[Joel Maher ( :jmaher ) (UTC -8)]

this bug should be resolved since we landed bug 680190.  If anybody has any other thoughts, please speak up

Comment 6

[Phil Ringnalda (:philor)]

Depends - if you want to call this bug a duplicate of that, and close it that way, we can clone it to a new "Tzoom failed to initialize browser" bug. But it only took me a couple of minutes to find https://tbpl.mozilla.org/php/getParsedLog.php?id=6306572 so it's certainly not the case that Tzoom never fails with "failed to initialize browser" as the overly-broad symptom anymore.

Comment 7

[Phil Ringnalda (:philor)]

And about half the extraordinary number of Android Talos failures right now are "failed to initialize browser" - should I open a separate new bug for each suite, or one new bug for every suite?

Comment 8

[Phil Ringnalda (:philor)]

I chose one, since that's less hassle for me: bug 686085