Closed Bug 823420 Opened 7 years ago Closed 7 years ago

Android mozilla-inbound perma-orange/red starting evening of Weds 12/19, with "Automation Error: No crash directory (/mnt/sdcard/tests/profile/minidumps/) found on remote device" and "talosError: 'failed to initialize browser'"

Categories

(Release Engineering :: General, defect, P2)

ARM
Android
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: dholbert, Assigned: nthomas)

References

Details

Starting with...
 https://tbpl.mozilla.org/?tree=Mozilla-Inbound&rev=06d72606ec56
...android has been perma-orange/red, with test runners all saying:
> Automation Error: No crash directory (/mnt/sdcard/tests/profile/minidumps/) found on remote device
...and with Talos runners all saying:
> talosError: 'failed to initialize browser'

I suspect infra issues, but I'm not sure. bz closed the tree, and I'm filing this bug to track the issue & any investigation.  (neither of us can actually dig into it further at the moment)
OS: Linux → Android
Hardware: x86_64 → ARM
Summary: Android perma-orange/red starting evening of Weds 12/19, with "Automation Error: No crash directory (/mnt/sdcard/tests/profile/minidumps/) found on remote device" and "alosError: 'failed to initialize browser'" → Android mozilla-inbound perma-orange/red starting evening of Weds 12/19, with "Automation Error: No crash directory (/mnt/sdcard/tests/profile/minidumps/) found on remote device" and "alosError: 'failed to initialize browser'"
Summary: Android mozilla-inbound perma-orange/red starting evening of Weds 12/19, with "Automation Error: No crash directory (/mnt/sdcard/tests/profile/minidumps/) found on remote device" and "alosError: 'failed to initialize browser'" → Android mozilla-inbound perma-orange/red starting evening of Weds 12/19, with "Automation Error: No crash directory (/mnt/sdcard/tests/profile/minidumps/) found on remote device" and "talosError: 'failed to initialize browser'"
Looks strongly correlated to the landings from bug 681805. Backed out 06d72606ec56 and 47debf3f344c.
Depends on: 681805
09:29:40 - edmorley|pto: nthomas: btw the backout will likely fix inbound; that message effectively translates to "didn't find the minidumps directory: either means automation/device issue, or else startup crash so we never got to the part where toolkit(?) creates the minidumps directory"
09:29:57 - edmorley|pto: I'll file a bug to make the string more clear
09:30:01 - nthomas: ok, I was thinking the latter
09:31:01 - nthomas: thanks for the confirmation
09:31:08 - edmorley|pto: nthomas: the real error shows in the logcat (further down the log) REPORTING UNCAUGHT EXCEPTION FROM THREAD 1 ("main")
09:31:13 - edmorley|pto: java.lang.RuntimeException: Unable to start activity ComponentInfo{org.mozilla.fennec/org.mozilla.fennec.App}: android.content.res.Resources$NotFoundException: Resource ID #0x7f0a0034
09:32:26 - edmorley|pto: I'll file a bug to get it added to the TBPL parser and/or see if we can get automation's checkForCrashes to check the logcat
tests are coming in green, inbound reopened.
Assignee: nobody → nthomas
Status: NEW → RESOLVED
Closed: 7 years ago
Priority: -- → P2
Resolution: --- → FIXED
I've filed bug 823452 to make the real failure mode clearer here.
Sorry the current situation led to the confusion! :-)
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.