1337784 - Autophone - svg busted with no measurements and no error message

Status: RESOLVED DUPLICATE of bug 1381511

(Testing Graveyard :: Autophone, defect)

Description

[Bob Clary [:bc] (inactive)]

https://treeherder.mozilla.org/#/jobs?repo=mozilla-inbound&revision=a75a77d1bb99e3238d422572fbf5e8fd102af8bb&filter-searchStr=autophone

https://treeherder.mozilla.org/logviewer.html#?job_id=75499619&repo=mozilla-inbound&lineNumber=127

https://autophone.s3.amazonaws.com/v1/task/LEUNRHVVS_G2ZplmPHJx8A/runs/0/artifacts/public/build/autophone-talos-tsvg-remote.ini-1-pixel-01-fc45d2af-858f-4121-94f7-efdf117c137d-logcat.log

It isn't clear to me why there is no TEST-UNEXPECTED-FAILURE message or why there were no measurements found.

jmaher: Want to look into it?

Comment 1

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

it appears that we startup the browser and do nothing after the first page load:
02-08 09:04:15.228 I/GeckoDump( 6614): Cycle 1(1): loaded http://10.252.73.230:8100/files/ep1/talos/tsvg/gearflowers.svg (next: http://10.252.73.230:8100/files/ep1/talos/tsvg/composite-scale.svg)
02-08 09:04:15.228 I/GeckoDump( 6614):
02-08 09:04:15.248 D/GeckoSuggestedSites( 6614): Number of suggested sites: 8
02-08 09:04:15.258 D/GeckoSuggestedSites( 6614): Number of suggested sites: 8
02-08 09:04:15.283 I/art     ( 6614): Do partial code cache collection, code=25KB, data=31KB
02-08 09:04:15.289 I/art     ( 6614): After code cache collection, code=22KB, data=29KB
02-08 09:04:15.289 I/art     ( 6614): Increasing code cache capacity to 128KB
02-08 09:04:15.313 W/View    ( 6614): requestLayout() improperly called by org.mozilla.gecko.home.TopSitesThumbnailView{d5431ee V.ED..... ......ID 13,13-509,296 #7f0901ab app:id/thumbnail} during layout: running second layout pass
02-08 09:04:16.332 I/GeckoDump( 6614): RSS: Main: 148459520
02-08 09:04:16.332 I/GeckoDump( 6614):

we load the page, dump the memory and seem to hang there- then somehow we die.  While this is not ideal, it isn't concerning that we hang/die- this could happen for many reasons- maybe the device had issues, maybe the browser had an unreported error, or maybe the server stopped sending pages.

I guess the question is why did we not get a failure message about timeout or missing data.  That would be the more realistic thing here to fix- it would be nice to know what happened here, did the browser hang? device crash? or we just got a timeout?  

Ideally I would fix this when there are 2 or 3 other instances of this- that would help point out above theories/questions.

Comment 2

[Bob Clary [:bc] (inactive)]

It looks like I covered all the bases to get a TEST-UNEXPECTED-FAIL but it didn't emit. This was the first test after the push. Maybe a stale pyc or something. We'll see if this repeats.