Closed Bug 1722416 Opened 3 years ago Closed 3 years ago

|mach android-emulator| won't create the emulator

Categories

(GeckoView :: General, defect)

Desktop
Linux
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 1722347

People

(Reporter: Gijs, Unassigned)

References

(Blocks 2 open bugs, Regression)

Details

(Keywords: regression)

+++ This bug was initially created as a clone of Bug #1722387 +++

Even with the patch from bug 1722387 cherry-picked, I cannot create or start an emulator.

Verbose ./mach android-emulator output:

gijs@gijs-ubuntu:~/mozilla-central$ ./mach android-emulator --version x86_64 --verbose
DEBUG: Running on Linux-5.11.0-25-generic-x86_64-with-glibc2.33
DEBUG: Emulator created with type x86_64
DEBUG: adb found at /home/gijs/.mozbuild/android-sdk-linux/platform-tools/adb
DEBUG:   ...with creation time Mon Jul 26 14:26:41 2021
DEBUG:   ...with SDK version in /home/gijs/.mozbuild/android-sdk-linux/platform-tools/source.properties: Pkg.Revision=31.0.2
 0:00.00 DEBUG ADBHost: {'_logger': <mozlog.structuredlog.StructuredLogger object at 0x7fdd1192e9d0>, '_verbose': True, '_use_root': True, '_adb_path': '/home/gijs/.mozbuild/android-sdk-linux/platform-tools/adb', '_adb_host': None, '_adb_port': None, '_timeout': 10, '_polling_interval': 0.001, '_adb_version': ''}
 0:00.01 DEBUG command_output: /home/gijs/.mozbuild/android-sdk-linux/platform-tools/adb devices -l, timeout: 10, timedout: None, exitcode: 0, output: List of devices attached
DEBUG: []
DEBUG: emulator found at /home/gijs/.mozbuild/android-sdk-linux/emulator/emulator
DEBUG:   ...with creation time Mon Jul 26 14:26:57 2021
DEBUG:   ...with SDK version in /home/gijs/.mozbuild/android-sdk-linux/emulator/source.properties: Pkg.Revision=30.7.5
 0:00.46 Starting Android emulator running Android x86_64...
DEBUG: emulator found at /home/gijs/.mozbuild/android-sdk-linux/emulator/emulator
DEBUG:   ...with creation time Mon Jul 26 14:26:57 2021
DEBUG:   ...with SDK version in /home/gijs/.mozbuild/android-sdk-linux/emulator/source.properties: Pkg.Revision=30.7.5
Error running mach:

    ['android-emulator', '--version', 'x86_64', '--verbose']

The error occurred in code that was called by the mach command. This is either
a bug in the called code itself or in the way that mach is calling it.
You can invoke |./mach busted| to check if this issue is already on file. If it
isn't, please use |./mach busted file android-emulator| to report it. If |./mach busted| is
misbehaving, you can also inspect the dependencies of bug 1543241.

If filing a bug, please include the full output of mach, including this error
message.

The details of the failure are as follows:

FileNotFoundError: [Errno 2] No such file or directory: '/home/gijs/.mozbuild/android-device/avd/mozemulator-x86_64.ini'

  File "/home/gijs/mozilla-central/mobile/android/mach_commands.py", line 554, in emulator
    emulator.start(gpu)
  File "/home/gijs/mozilla-central/testing/mozbase/mozrunner/mozrunner/devices/android_device.py", line 620, in start
    self._update_avd_paths()
  File "/home/gijs/mozilla-central/testing/mozbase/mozrunner/mozrunner/devices/android_device.py", line 770, in _update_avd_paths
    with open(ini_path, "r") as f:

./mach mochitest is much more summary:

gijs@gijs-ubuntu:~/mozilla-central$ ./mach mochitest
No Android devices connected. Start an emulator? (Y/n) 
Android AVD not found, please run |mach bootstrap|

... but I have run mach bootstrap - in fact, by now I have run it about 5 times. It doesn't seem to make a difference. It says:

Looks like you have the correct version of the Android NDK installed at:
/home/gijs/.mozbuild/android-ndk-r21d


Looks like you have the Android SDK installed at:
/home/gijs/.mozbuild/android-sdk-linux
We will install all required Android packages.


We are now installing the following Android packages:
platform-tools
build-tools;30.0.2
platforms;android-30
You may be prompted to agree to the Android license. You may see some of
output as packages are downloaded and installed.

[=======================================] 100% Computing updates...             

Looks like you have the correct version of the Android NDK installed at:
/home/gijs/.mozbuild/android-ndk-r21d


Looks like you have the Android SDK installed at:
/home/gijs/.mozbuild/android-sdk-linux
We will install all required Android packages.


We are now installing the following Android packages:
emulator
system-images;android-24;default;x86_64
You may be prompted to agree to the Android license. You may see some of
output as packages are downloaded and installed.

[=======================================] 100% Computing updates...             

Looks like you have the correct version of the Android NDK installed at:
/home/gijs/.mozbuild/android-ndk-r21d


Looks like you have the Android SDK installed at:
/home/gijs/.mozbuild/android-sdk-linux
We will install all required Android packages.


We are now installing the following Android packages:
emulator
system-images;android-24;default;armeabi-v7a
You may be prompted to agree to the Android license. You may see some of
output as packages are downloaded and installed.

[=======================================] 100% Computing updates...        

I also tried to install android studio, which seems to have made no difference. I don't know enough about android studio to figure out how to help me run the steps in https://firefox-source-docs.mozilla.org/mobile/android/geckoview/contributor/for-gecko-engineers.html#configuring-the-build-system - the steps in https://firefox-source-docs.mozilla.org/mobile/android/geckoview/contributor/native-debugging.html also appear to skip over the "how to make android studio recognize the source tree" part (should I import from VCS? From a gradle file? Something else?), and the options AVD manager gives also don't seem to line up with mozemulator-x86_64 thingy we want here.

I believe this is should be fixed by Bug 1722347. Please reopen if not.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
Has Regression Range: --- → yes
Keywords: regression
You need to log in before you can comment on or make changes to this bug.