Closed Bug 1338807 Opened 7 years ago Closed 3 years ago

xpcshell tests fail on physical device with SELinux enabled

Categories

(Firefox for Android Graveyard :: Testing, defect, P5)

All
Android
defect

Tracking

(firefox54 affected)

RESOLVED INCOMPLETE
Tracking Status
firefox54 --- affected

People

(Reporter: JanH, Unassigned)

References

()

Details

I've got a Moto G4 Play with Android 6.0.1 and despite being rooted xpcshell tests fail to run in the default configuration:

DMError: Error pushing file /home/jan/Mozilla/mozilla-central/objdir-droid/dist/bin/xpcshell -> /data/local/xpcb/xpcshell; output: ['[ 22%] /data/local/xpcb/xpcshell', '[ 44%] /data/local/xpcb/xpcshell', '[ 66%] /data/local/xpcb/xpcshell', '[ 89%] /data/local/xpcb/xpcshell', '[100%] /data/local/xpcb/xpcshell', "adb: error: failed to copy '/home/jan/Mozilla/mozilla-central/objdir-droid/dist/bin/xpcshell' to '/data/local/xpcb/xpcshell': Permission denied"]

Switching the SELinux mode to "permissive" makes things working again, so maybe the test harness could check the current SELinux mode, set it to "permissive" if necessary and restore the original state again afterwards.
Changing the SELinux mode isn't persistent so there is no need to restore really. It will be reset after the next boot anyway.
Sure, but from a UX point of view rebooting is more of a hassle than just flipping it back on.
See Also: → 1375076
Android xpcshell tests have been converted to adb_android.py, so this *might* just work now.
gbrown: You mean the work I am doing for android hardware? Apart from the crash, maybe. :-)
Heh. Right.

I was thinking that bug 1440714 has converted the xpcshell harness to use adb.py, which includes a setenforce call, so it should/might not have trouble pushing files to device, the way comment 0 was complaining about.

*But* we also recently discovered that xpcshell is crashing on Android 7 devices - bug 1451930. It works fine on Android 4.3. Not sure about other Android versions.
Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195

Needinfo :susheel if you think this bug should be re-triaged.
Priority: P3 → P5
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.