Closed
Bug 1983294
Opened 10 months ago
Closed 10 months ago
use newer android 14 emulator for pgo
Categories
(Testing :: General, task)
Testing
General
Tracking
(firefox144 fixed)
RESOLVED
FIXED
144 Branch
| Tracking | Status | |
|---|---|---|
| firefox144 | --- | fixed |
People
(Reporter: jmaher, Assigned: jmaher)
References
Details
Attachments
(1 file)
No description provided.
| Assignee | ||
Comment 1•10 months ago
|
||
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)
Comment 2•10 months ago
|
||
A few thoughts..
- We seem to be using emulator 32.1.15.0 which is about two years out of date. https://developer.android.com/studio/releases/emulator#32-1-15
- We can try to update the emulator, but that looks tangled up in dropping Android 7. https://searchfox.org/mozilla-central/rev/59cf9b740d7f5db77c595d0c886734780bfb257b/taskcluster/scripts/misc/repack-android-emulator-linux.sh#13-14 . It isn't clear that that is what is blocking us though, but we could have multiple emulators staged if we need.
- The live.log shows that mozharness times out before successfully booting. We could try bumping the timeout if the modern images are just slow to boot. https://searchfox.org/mozilla-central/source/testing/mozharness/mozharness/mozilla/testing/android.py#221
- The
ERROR | Running multiple emulators with the same AVDmessage seems to be tied to us restarting the emulator a few times without cleanly shutting down the previous time. This is kind of gross, but we probably want to just ignore this if we can get the emulator to actually boot the first time.
Start with bumping the 330s timeout to something much larger and see if the screenshots show better progress through boot.
Flags: needinfo?(tcampbell)
| Assignee | ||
Comment 3•10 months ago
|
||
Updated•10 months ago
|
Assignee: nobody → jmaher
Status: NEW → ASSIGNED
Pushed by jmaher@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/ee102e926521
https://hg.mozilla.org/integration/autoland/rev/5a64202e6a77
Use newer Android 14 emulator to run pgo profiling. r=tcampbell
Comment 5•10 months ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 10 months ago
status-firefox144:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 144 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•