Closed Bug 1983294 Opened 10 months ago Closed 10 months ago

use newer android 14 emulator for pgo

Categories

(Testing :: General, task)

task

Tracking

(firefox144 fixed)

RESOLVED FIXED
144 Branch
Tracking Status
firefox144 --- fixed

People

(Reporter: jmaher, Assigned: jmaher)

References

Details

Attachments

(1 file)

No description provided.

I am having trouble with this. here is a try push that the run job is blue and keeps retrying, basically the emulator is not able to startup.

I see stuff in the emulator logs:

INFO    | Android emulator version 32.1.15.0 (build_id 10696886) (CL:N/A)
INFO    | Found systemPath /builds/worker/fetches/android-sdk-linux/system-images/android-34/google_apis/x86_64/
WARNING | Please update the emulator to one that supports the feature(s): SupportPixelFold
ERROR   | Running multiple emulators with the same AVD 
ERROR   | is an experimental feature.
ERROR   | Please use -read-only flag to enable this feature.
INFO    | Storing crashdata in: /tmp/android-worker/emu-crash.db, detection is enabled
INFO    | Duplicate loglines will be removed, if you wish to see each indiviudal line launch with the -log-nofilter flag.
VERBOSE | autoconfig: -skindir (null)
VERBOSE | autoconfig: -kernel /builds/worker/fetches/android-sdk-linux/system-images/android-34/google_apis/x86_64//kernel-ranchu
VERBOSE | Target arch = 'x86_64'
VERBOSE | Auto-detect: Kernel image requires new device naming scheme.
VERBOSE | Auto-detect: Kernel does not support YAFFS2 partitions.
VERBOSE | autoconfig: -ramdisk /builds/worker/fetches/android-sdk-linux/system-images/android-34/google_apis/x86_64//ramdisk.img
VERBOSE | Using initial system image: /builds/worker/fetches/android-sdk-linux/system-images/android-34/google_apis/x86_64//system.img
VERBOSE | Using initial vendor image: /builds/worker/fetches/android-sdk-linux/system-images/android-34/google_apis/x86_64//vendor.img
VERBOSE | autoconfig: -data /builds/worker/fetches/android-device/avd/mozemulator-android34-x86_64.avd/userdata-qemu.img
VERBOSE | autoconfig: -initdata /builds/worker/fetches/android-device/avd/mozemulator-android34-x86_64.avd/userdata.img
VERBOSE | autoconfig: -cache /builds/worker/fetches/android-device/avd/mozemulator-android34-x86_64.avd/cache.img
VERBOSE | Physical RAM size: 3072MB
VERBOSE | VM heap size 0MB is below hardware specified minimum of 576MB,setting it to that value
VERBOSE | System image is read only
VERBOSE | Found 1 DNS servers:
VERBOSE | 	169.254.169.254

overall it looks like things are working (no glaring errors), but obviously something is wrong. Maybe other logs could help out.

Ted, would you have some ideas as to why this is happening and what we could do to get this to work?

Flags: needinfo?(tcampbell)

A few thoughts..

Start with bumping the 330s timeout to something much larger and see if the screenshots show better progress through boot.

Flags: needinfo?(tcampbell)
Assignee: nobody → jmaher
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 10 months ago
Resolution: --- → FIXED
Target Milestone: --- → 144 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: