It doesn't make sense that the IDs used in the status command and log filenames use the MAC address. They should use the serial number like we do in other places.

As reported in the last issue, somehow the runbrowserprofile.sh script became inaccessible; however, autophone never noticed the error:

$ adb -s 0A3A8EB60D02201D shell sh /data/data/com.mozilla.SUTAgentAndroid/files/tests/autophone/runbrowserprofile.sh org.mozilla.fennec/.App /data/data/com.mozilla.SUTAgentAndroid/files/tests/autophone/profile file://mnt/sdcard/s1test/startup6.html
sh: Can't open /data/data/com.mozilla.SUTAgentAndroid/files/tests/autophone/runbrowserprofile.sh

AutoPhone should be checking the results of the adb command to verify that it worked. We probably need an ERROR or DISABLED state as well.

Please can you update treeherder-client to the latest release (4.0.0) to pick up changes to which API endpoints are used (the old endpoints will be disabled at some point in the future):

The changelog can be found here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1387711#c2

Many thanks!

It would be nice to be able to terminate the tests on a particular phone.

Downloading/unpacking logparser (from -r requirements.txt (line 4))
Could not find any downloads that satisfy the requirement logparser (from -r requirements.txt (line 4))
Cleaning up...
No distributions at all found for logparser (from -r requirements.txt (line 4))
Storing debug log for failure in /Users/shawn.mccarthy/.pip/pip.log

Somehow this happened:

$ ls -l /data/data/com.mozilla.SUTAgentAndroid/files/
-rw------- app_113 app_113 102 2012-04-07 11:27 SUTAgent.ini
drwx------ app_113 app_113 2012-04-07 11:27 tests

Since the tests directory somehow became accessible only to the app_113 user, the shell command to launch runbrowserprofile.sh failed:

$ sh /data/data/com.mozilla.SUTAgentAndroid/files/tests/autophone/runbrowserprofile.sh org.mozilla.fennec/.App /data/data/com.mozilla.SUTAgentAndroid/files/tests/autophone/profile file://mnt/sdcard/s1test/startup6.html
sh: Can't open /data/data/com.mozilla.SUTAgentAndroid/files/tests/autophone/runbrowserprofile.sh

Unfortunately autophone didn't notice this error (see issue #2).

FYI: The following changes were made to this repository's wiki:

• defacing spam has been removed

• the wiki has been disabled, as it was not used

These were made as the result of a recent automated defacement of publically writeable wikis.

Apparently the reliability of adb can be improved by stopping and starting the adb server before and after test runs.

It would be super to be able to resume jobs if autophone is killed. I think it would be too tricky to figure out exactly where we are in a given test, so we should just redo the jobs for the current build when it's restarted.

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please reach out to [email protected].

(Message COC001)

Several Mozilla projects now use https://pyup.io/ to automatically open PRs when their Python packages have new releases available. Perhaps it's a good fit for this project too?

Search for "pyup" in this guide for more info:
https://wiki.mozilla.org/Security/FirefoxOperations#Security_Checklist

(Context: keeping the treeherder-client package up to date to help the Treeherder team deprecate API features more expediently)

Many thanks!

When a phone is re-enabled, it goes through all queued jobs. However the current job isn't queued. It should be, unless it was an error in the test (i.e. not an android error), if we can tell that.

Both Autophone's throbber gradle jobs and python's taskgraph job use 'tg' as job symbol (but in different groups). Please use a different one, e.g. thg