Closed Bug 807416 Opened 8 years ago Closed 8 years ago

installing XPCShell tests fails to chmod files

Categories

(Testing :: XPCShell Harness, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: bjacob, Unassigned)

References

Details

While installing XPCShell tests with devicemanagerADB I get messages like this:

Unable to chmod /mnt/sdcard/tests/xpcshell/b/libnssutil3.so: Operation not permitted
chmod /mnt/sdcard/tests/xpcshell/b/libnssutil3.so
Unable to chmod /mnt/sdcard/tests/xpcshell/b/libomxplugin.so: Operation not permitted
chmod /mnt/sdcard/tests/xpcshell/b/libomxplugin.so
Unable to chmod /mnt/sdcard/tests/xpcshell/b/libplc4.so: Operation not permitted
chmod /mnt/sdcard/tests/xpcshell/b/libplc4.so

The device is a Nexus S rooted with CyanogenMod.

The command I used was

export DM_TRANS=adb
make -C obj-mobile-debug/toolkit/mozapps/extensions/test/ xpcshell-tests-remote

Problem persists after emptying /mnt/sdcard/tests
Blocks: 806369
AFAIK it is impossible to run xpcshell tests from /mnt/sdcard/tests -- you must use /data/local/tests. The way to do that is to create /data/local/tests manually first:

> adb shell mkdir /data/local/tests
> make xpcshell-tests-remote

(That's documented at https://wiki.mozilla.org/Mobile/Fennec/Android#xpcshell)

The blocking issue is that AFAIK it is impossible to change the permissions on a file on /mnt/sdcard to add execute permission -- which is essential to execute the xpcshell binary.
Ah, I see. This same page,

  https://wiki.mozilla.org/Mobile/Fennec/Android#Testing

says:
 
  If, and only if, you can't mount an sdcard for whatever reason run:
  mkdir /data/local/tests

Since it didn't seem to have trouble mounting the sdcard, I thought I shouldn't use /data/local.
I updated that wiki to try to clarify.
Other than the wiki update, I think there's nothing to be done for this bug: We cannot run xpcshell tests from the sdcard.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.