1837710 - Local run of web platform test on Android hangs

Status: NEW

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

Description

[Botond Ballo [:botond]]

Attachment: Complete command line output

Steps to reproduce

1. Build Firefox for Android in debug mode (ARM device build).
2. Attach an Android device via USB cable.
3. Run ./mach wpt testing/web-platform/tests/css/css-overscroll-behavior/overscroll-behavior.html

Actual results

The command gets as far as BUILD SUCCESSFUL followed by adb INFO Setting run_as_package to org.mozilla.geckoview.test_runner, and then hangs.

Please see complete output, and Android log, attached.

Comment 1

[Botond Ballo [:botond]]

Attachment: Android log

Comment 2

[James Graham [:jgraham]]

Can you successfully run on Android using the emulator (just to help narrow down the problem here; I understand that you might need the device to reproduce your bug)?

Comment 3

[Botond Ballo [:botond]]

(In reply to James Graham [:jgraham] from comment #2)

Can you successfully run on Android using the emulator (just to help narrow down the problem here; I understand that you might need the device to reproduce your bug)?

Confirmed, the test runs successfully in the emulator, so this seems to be a device-specific issue.

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:jgraham, could you have a look please?

For more information, please visit BugBot documentation.

Comment 5

[James Graham [:jgraham]]

OK, This might be a mozdevice issue; wpt shouldn't be doing anything too special with android. Are you able to run other test harnesses?

Comment 6

[Botond Ballo [:botond]]

(In reply to James Graham [:jgraham] from comment #5)

Are you able to run other test harnesses?

The other test suites that I've tried on a device build are:

• geckoview-junit: works fine
• mochitest: fails, though with different symptoms (errors rather than a hang); I filed bug 1803027 for this

Everything works fine in an emulator build.

For the time being, I've taken to maintaining two Android builds: an emulator build for test debugging, and a device build for interactive debugging. As a result, this and bug 1803027 are not blocking me from making progress on anything; however, it would be more efficient and a nicer workflow to be able to do it all with a single (device) build.