CPU EMULATOR ENGINE MAC INSTALL
I'm loathe to install the emulator machinery as part of bootstrap, since it's not part of _building_ but part of _testing_. Seems like some sort of change to how the sdk is packaged, or how > present, but /tools/emulator64-arm and related binaries were all
> We looked into this a little and found that /tools/emulator was (In reply to Geoff Brown (pto Aug 19 - Aug 27) from comment #1) > File "/home/mstange/code/mozilla-central/testing/mozbase/mozdevice/mozdevice/devicemanager.py", line 415, in shellCheckOutput > File "/home/mstange/code/mozilla-central/testing/mozbase/mozrunner/mozrunner/devices/android_device.py", line 141, in verify_android_device > verify_android_device(self, install=True) > File "/home/mstange/code/mozilla-central/python/mozbuild/mozbuild/mach_commands.py", line 1341, in run > DMError: Non-zero return code for command: (output: '', retval: 'None') > The details of the failure are as follows: > If filing a bug, please include the full output of mach, including this error
> You should consider filing a bug for this issue. > a bug in the called code itself or in the way that mach is calling it. > The error occurred in code that was called by the mach command. > WARNING: See log at /home/mstange/.mozbuild/android-device/emulator.log and/or use -verbose for more information. > WARNING: Emulator has already completed!
home/mstange/.mozbuild/android-device/emulator.log contains one line: "AVD" was downloaded by "mach run" just before I tried to run "mach mochitest". After compiling Firefox for Android, I tried to run mochitests in the emulator. I used mach bootstrap to create a build environment for "Firefox for Android" builds.
0 kommentar(er)
