Unpin android emulator
Categories
(Release Engineering :: General, enhancement)
Tracking
(Not tracked)
People
(Reporter: gbrown, Assigned: gbrown)
References
Details
Attachments
(1 obsolete file)
In bug 1868944 we pinned the android emulator to an earlier version, since the latest version of the emulator would not start. Can we remove that hack and use the latest version?
![]() |
Assignee | |
Comment 1•2 years ago
|
||
From bug 1868944:
Screenshot artifacts for the failed tasks show an emulator pop-up: title="Emulator Running in Nested Virtualization", body="The emulator is running using nested virtualization. This is not recommended. It may not work at all. And typically the performance is not quite good.", check-box="Never show this again." (unchecked).
Recent (yesterday's) successful android-em test tasks have emulator logs that show:
Android emulator version 32.1.15.0 (build_id 10696886) (CL:N/A)
The failing tasks' emulator logs have:
Android emulator version 33.1.23.0 (build_id 11150993) (CL:N/A)
...The emulator even has an override for that warning: --no-nested-warnings
![]() |
Assignee | |
Comment 2•2 years ago
|
||
Updated•2 years ago
|
![]() |
Assignee | |
Comment 3•2 years ago
|
||
The emulator still doesn't start with -no-nested-warnings. I can't think of anything else to try, except to keep with the older emulator version.
Description
•