wpt wants to run geckoview testing (and eventually Chrome Android testing) to get mobile-specific interop results. This means doing periodic (likely daily) runs of upstream wpt on android. We intend to use a similar setup to gecko where the tests are running inside a docker image on the x86_64 emulator. Once that all works we need to be able to access the pool of android machines from the wpt project, and configure our runs so that those jobs are scheduled on the correct kinds of hardware.

It's assumed that this will happen after TC does the gecko/not-gecko migration.

Per jmaher, there should be enough capacity on packet.net to allow daily runs of the two browsers without causing significant issues.

I think we'll need to get some access to android emulators, which need to run on bare-metal. It turns out that packet.net is slightly worse than being hit in the head with a rPi, so we'll want to do that on AWS bare-metal instances, bug 1578460.

I don't think we ever completed this, but no traffic for a year ..