Closed Bug 1521624 Opened 11 months ago Closed 10 months ago

./mach wpt on Android x86 emulator gets stuck after launching the Firefox

Categories

(Testing :: web-platform-tests, defect)

defect
Not set

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: hiro, Unassigned)

References

Details

Attachments

(4 files)

Attached file wpt.log

From bug 1511764 comment 8;

The environment I am using is Linux x64 just setup today with ./mach bootstrap for "GeckoView/Firefox for Android". The revision is https://hg.mozilla.org/mozilla-central/rev/666abafd77b1 .

Also note that ./mach mochitest or other ./mach command works fine.

Note that the Firefox process is correctly launched by ./mach wpt and can load http://web-platform.test:8000/testharness_runner.html with inputting the URL by hand. So the test runner gets lost the connection with the Firefox process?

Anyway I am attaching a log on console, will attach a log got by 'adb logcat |grep Gecko' in the next comment.

Attached file adb.log

There shouldn't be a networking problem if you are using the emulator. I don't know what is going wrong for you.

I could not reproduce this. I did this, with an android x86 build:

$ ./mach android-emulator --force-update
$ ./mach install
$ adb logcat -c
$ ./mach wpt testing/web-platform/tests/css/css-device-adapt/ > wptlog 2>&1
$ adb logcat -d > wptlogcat

Will attach my logs for comparison.

Attached file geoff's adb.log

Is that still a problem with bug 1511764 fixed?

Flags: needinfo?(hikezoe)

Note again that bug 1511764 only fixed an attempt to use marionette after starting the session already failed. It didn't affect whatever the underlying issue is that prevents the session starting.

Still no luck. It gets stuck after firefox is launched.

Flags: needinfo?(hikezoe)

Are you using Fennec or GeckoView? Can you please add a new log file? The failure details should be more clear now.

Looking at the original logs again, I notice that there are no Marionette statements in the logcat. Possibly marionette is disabled in :hiro's build? (mozconfig needs "ac_add_options --enable-marionette" to enable marionette for wpt tests)

(In reply to Geoff Brown [:gbrown] from comment #9)

Looking at the original logs again, I notice that there are no Marionette statements in the logcat. Possibly marionette is disabled in :hiro's build? (mozconfig needs "ac_add_options --enable-marionette" to enable marionette for wpt tests)

Gosh! I didn't specify the option at all... Now I am building with the option.

It works!!! Thank you, Geoff!

Status: NEW → RESOLVED
Closed: 10 months ago
Resolution: --- → INVALID

Wait, is Marionette not implied enabled on Android these days?

I think so. The environment was just setup when I reported this bug. The .mozconfig I used was;

Build GeckoView/Firefox for Android:

ac_add_options --enable-application=mobile/android

Targeting the following architecture. Ensure exactly one --target is uncommented!

For regular phones:

ac_add_options --target=arm-linux-androideabi

For x86 emulators (and x86 devices, which are uncommon):

ac_add_options --target=i686-linux-android

For newer phones.

ac_add_options --target=aarch64-linux-android

For x86_64 emulators (and x86_64 devices, which are even less common):

ac_add_options --target=x86_64-linux-android

ac_add_options --enable-debug
ac_add_options --enable-optimize
ac_add_options --enable-tests

With the following Android SDK and NDK:

ac_add_options --with-android-sdk="/home/hiro/.mozbuild/android-sdk-linux"
ac_add_options --with-android-ndk="/home/hiro/.mozbuild/android-ndk-r17b"

With the following compiler toolchain:

CC="/home/hiro/.mozbuild/clang/bin/clang"
CXX="/home/hiro/.mozbuild/clang/bin/clang++"

(In reply to Andreas Tolfsen ⦗:ato⦘ from comment #12)

Wait, is Marionette not implied enabled on Android these days?

Only in that --enable-marionette is in the standard mozconfig variants:

https://searchfox.org/mozilla-central/rev/05d4b6962a571585bd679d2bbb0df0a5fb4e4eff/mobile/android/config/mozconfigs/common#38

You need to log in before you can comment on or make changes to this bug.