Bugzilla

Bug 1547135 added functionality to configure specific Android devices for performance tests.  That code landed as part of device setup in [`testing/raptor/raptor.py`](https://searchfox.org/mozilla-central/rev/0671407b7b9e3ec1ba96676758b33316f26887a4/testing/raptor/raptor/raptor.py#748-917) but there is nothing Raptor-specific (indeed, nothing harness-specific) about this configuration.  This ticket tracks lifting it to higher up the stack for re-use.

Exactly where to put it is less clear to me.  I think this functionality is not very general -- it's tied to two reference devices and probably depends on details of how they are rooted by Mozilla's operations team -- and therefore probably doesn't want to live in `mozdevice`.  Maybe a sibling of `mozdevice`?

In any case, this should be invoked by [`raptor.py`](https://searchfox.org/mozilla-central/source/testing/mozharness/mozharness/mozilla/testing/raptor.py) as part of general device configuration appropriate for performance tests.

Bug 1547135 added functionality to configure specific Android devices for performance tests.  That code landed as part of device setup in [`testing/raptor/raptor.py`](https://searchfox.org/mozilla-central/rev/0671407b7b9e3ec1ba96676758b33316f26887a4/testing/raptor/raptor/raptor.py#748-917) but there is nothing Raptor-specific (indeed, nothing harness-specific) about this configuration.  This ticket tracks lifting it to higher up the stack for re-use.

Exactly where to put it is less clear to me.  I think this functionality is not very general -- it's tied to two reference devices and probably depends on details of how they are rooted by Mozilla's operations team -- and therefore probably doesn't want to live in `mozdevice`.  Maybe a sibling of `mozdevice`?

In any case, this should be invoked by [`mozharness raptor.py`](https://searchfox.org/mozilla-central/source/testing/mozharness/mozharness/mozilla/testing/raptor.py) as part of general device configuration appropriate for performance tests.