Open Bug 1932631 Opened 1 year ago Updated 1 year ago

`./mach wpt` does not run tests on an Android real device

Categories

(GeckoView :: General, task, P5)

All
Android
task

Tracking

(Not tracked)

People

(Reporter: olivia, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file, 1 obsolete file)

When trying to run ./mach wpt webcodecs:

  • On an emulated device, the test loads and runs as expected.

  • On a real physical device, the logs get stuck at:
    0:48.48 adb INFO Setting run_as_package to org.mozilla.geckoview.test_runner

./mach geckoview-junit runs as expected on a real device.
Device is an Android 14 Pixel 4a.

Attached file startup.log (obsolete) —
Attached file startup.log

Problems listed at file:///Users/olivia/Repos/gecko/obj-aarch64-unknown-linux-android/gradle/build/reports/problems/problems-report.html were build lint warnings and the like.

Attachment #9439097 - Attachment is obsolete: true
Attachment #9439098 - Attachment mime type: application/octet-stream → text/plain

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

For more information, please visit BugBot documentation.

Flags: needinfo?(bugzeeeeee)
Severity: -- → N/A
Type: defect → task
Flags: needinfo?(bugzeeeeee)
Priority: -- → P5

Have some follow-up information :adhingra discovered:

Paraphrasing:
It looks like device serial isn't passed. A workaround is to paste the id from adb devices here.

The emulator was hardcoded here.

--device-serial may also be used.

This is not sufficient.

./mach wpt --package-name org.mozilla.fenix.debug --device-serial 39271FDJH00A7H testing/web-platform/tests/resource-timing/initiator-type/input.html

This harness has never worked with actual android devices.

Do we know if there's a conceptual blocker, i.e., not just misconfiguration; or do we know that there is no conceptual blocker (perhaps because :olivia has made it work on a device); or do we not know one way of the other?

Flags: needinfo?(ohall)

Thanks for taking a look!

It sounded like :padenot managed a workaround to get it to run on a real device (based on this Slack thread for more context). :jgraham had some more context too. There didn't seem to be a specific reason wpt tests should not run on real devices, more just that they hadn't been fully plumbed in.

(I'm not sure about org.mozilla.fenix.debug as mentioned in Comment 5, though. I was under the impression that in the first case that they were also running org.mozilla.geckoview.test_runner.)

Flags: needinfo?(ohall)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: