Closed Bug 702980 Opened 13 years ago Closed 13 years ago

android crashtests are failing at 37% test 372 quite frequently on m-c

Categories

(Firefox for Android Graveyard :: General, defect)

Product:
Firefox for Android Graveyard
Component:
General
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: jmaher, Assigned: mbrubeck)

Details

(Whiteboard: [android][tegra][mobile_unittests])

we need to look into this further, but I am seeing an increase in C1 crashes where the previous week we had none. I suspect we will have to disable tests with if(android) clauses in a manifest, but that is not preferred. If the mobile dev team isn't going to look into this with their new found focus on nativeUI fennec, we should just do a disable of the faulty test instead of trying to fix it.
yup, disable it
Whiteboard: [android][tegra][mobile_unittests][mobile_dev_needed] → [android][tegra][mobile_unittests]
Assignee: nobody → mbrubeck
I have been unable to reproduce this locally, although after looking in the logs, this seems common: REFTEST TEST-START | http://10.250.48.210:30070/tests/content/xul/templates/src/crashtests/329335-1.xul | 372 / 984 (37%) REFTEST TEST-PASS | http://10.250.48.210:30070/tests/content/xul/templates/src/crashtests/329335-1.xul | (LOAD ONLY) REFTEST INFO | before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 before 368640, after 368640, break 057ff000 Loading a blank page REFTEST TEST-START | http://10.250.48.210:30070/tests/content/xul/templates/src/crashtests/329884-1.xul | 373 / 984 (37%) REFTEST TEST-PASS | http://10.250.48.210:30070/tests/content/xul/templates/src/crashtests/329884-1.xul | (LOAD ONLY) So the concerning thing is all the "before 368640, after 368640, break 057ff000" statements. We never see much of that anymore except right where we are failing regularly. Unfortunately we fail in different spots, just commonly here. While trying to reproduce this (11 runs so far with no error), I didn't see the before/after/break messages, nor did I see the browser hang. You can find other log files in bug 663657.
Crashtest failures seem to have fallen to below 1% recently, with zero C1 failures in the past week: http://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=663657&startday=2011-11-01&endday=2011-11-29&tree=mozilla-inbound Resolving for now; I'll reopen if this failure happens again.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.