1803027 - Android mochitest run fails with repeated "No such file or directory" errors

Status: NEW

(Testing :: Mochitest, defect, P3)

Description

[Botond Ballo [:botond]]

Attachment: Command output

STR

1. Build recent mozilla-central for Android
2. Run a mochitest, e.g. ./mach mochitest gfx/layers/apz/test/mochitest/test_group_mainthread.html

Actual results

The test run gets as far as launching the "GeckoView Test Runner" app on the device or emulator, but then starts to produce the following error repeatedly:

1:43.16 adb ERROR pull /data/local/tmp/tmpva5bvcdx /tmp/tmpo2rs31jw: args: /home/botond/.mozbuild/android-sdk-linux/platform-tools/adb wait-for-device shell run-as org.mozilla.geckoview.test_runner cp -R /data/data/org.mozilla.geckoview.test_runner/test_root/logs/mochitest.log /data/local/tmp/tmpva5bvcdx, exitcode: 1, stdout: cp: bad '/data/data/org.mozilla.geckoview.test_runner/test_root/logs/mochitest.log': No such file or directory

See attachment for full output

Comment 1

[Botond Ballo [:botond]]

This happens with both a device build and an emulator build.

Comment 2

[Geoff Brown [:gbrown]]

Sorry :botond, but I cannot reproduce the problem: ./mach mochitest gfx/layers/apz/test/mochitest/test_group_mainthread.html runs successfully for me, with a recent m-c build, android emulator, and running on Ubuntu.

I wonder if the test runner app is crashing? Running "adb logcat" in another terminal while running the mochitest might tell us more.

Comment 3

[Hiroyuki Ikezoe (:hiro)]

Probably this part is a clue.

 1:42.73 WARNING Failed wait for remote log: /data/data/org.mozilla.geckoview.test_runner/test_root/logs/mochitest.log missing?

Comment 4

[Botond Ballo [:botond]]

Seems to be working fine in an emulator build now. My device build is on a machine affected by bug 1802618, maybe this was a complication of that; I'll re-test there once I've sorted that out.

Comment 5

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

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

For more information, please visit auto_nag documentation.

Comment 7

[Botond Ballo [:botond]]

(In reply to Botond Ballo [:botond] from comment #4)

My device build is on a machine affected by bug 1802618, maybe this was a complication of that; I'll re-test there once I've sorted that out.

Unfortunately, after sorting bug 1802618 out, my device build is still affected by this, i.e. I'm not able to run mochitests on my device build. (Other tests like geckoview-junit work fine.)

Comment 8

[[:owlish] 🦉 PST]

(In reply to Botond Ballo [:botond] from comment #1)

This happens with both a device build and an emulator build.

[duplicating our Matrix chat here for visibility] I tested on emulator, and I was able to run the tests with no problem, so emulator builds should work. I'll try device builds.

Comment 9

[Botond Ballo [:botond]]

(In reply to [:owlish] 🦉 PST from comment #8)

I tested on emulator, and I was able to run the tests with no problem, so emulator builds should work.

I did re-test this as well with a fresh emulator build, and can confirm that it works fine, so this issue is specific to device builds.