Confirmed users
3,990
edits
ReleaseEngineering/Platforms/Android: Difference between revisions
ReleaseEngineering/Platforms/Android (view source)
Revision as of 16:03, 21 January 2014
, 21 January 2014→Testing
| Line 25: | Line 25: | ||
We run '''unit tests''' and '''performance''' tests on Tegra development boards. | We run '''unit tests''' and '''performance''' tests on Tegra development boards. | ||
NOTE: Tegra boards are armv7, however, we can run armv6 builds on it. | NOTE: Tegra boards are armv7, however, we can run armv6 builds on it. | ||
== Android 2.3 on EC2 == | |||
This is still WIP. | |||
We want to run Android 2.3 '''unit tests''' on EC2 Ubuntu 64-bit instances (tst-linux64-spot-XXX or tst-linux64-ec2-XXX). | |||
We have written [[https://wiki.mozilla.org/ReleaseEngineering/Mozharness|Mozharness] code to start up four Android emulators on these hosts and run on each emulator a different test suite. This means that we can run up to four different test jobs on the same host cutting the load on the pool. | |||
Each emulator starts up with a specific avd definition that already has the SUT agent and Watcher (TODO add link to docs). | |||
These AVD definitions are stored on a tar ball which we store on tooltool (TODO add link to docs), which we download to the host if it is not already cached and untar on every job to have a clean state for the emulators to start from. | |||
TODO: explain what AVD definitions are. | |||
We deploy the Android SDK 18 (TODO add link) with puppet (TODO add link) before the machine starts a job. | |||
TODO finish this up | |||
=== Deployment of artifacts === | |||
* TODO: Link to how to deploy a new version of the Android SDK | |||
* [[ReleaseEngineering:Buildduty:Other_Duties#How_to_upload_to_Tooltool|How to upload a new AVD definition to ToolTool]] | |||
=== How to build the emulator === | |||
TODO: add info | |||
=== How to generate patched Android SDK === | |||
TODO: add info | |||
=== How to generate the AVD definitions === | |||
TODO: add info | |||
== Android 4.0 Armv7 == | == Android 4.0 Armv7 == | ||
| Line 32: | Line 56: | ||
== Android 4.2 x86 == | == Android 4.2 x86 == | ||
We run '''unit tests''' and '''performance''' tests on in-house Ubuntu 64-bit hosts (talos-linux64-ix-XXX). | We run '''unit tests''' and '''performance''' tests on in-house Ubuntu 64-bit hosts (talos-linux64-ix-XXX). | ||
We have written [[https://wiki.mozilla.org/ReleaseEngineering/Mozharness|Mozharness] code to start up | We have written [[https://wiki.mozilla.org/ReleaseEngineering/Mozharness|Mozharness] code to start up four Android emulators on these hosts and run on each one a different test suites. This means that we can run up to four different test jobs on the same host cutting the load on the pool. | ||
Each emulator starts up with a specific avd definition that already has the SUT agent and Watcher (TODO add link to docs). | Each emulator starts up with a specific avd definition that already has the SUT agent and Watcher (TODO add link to docs). | ||
These AVD definitions are stored on a tar ball which we store on tooltool (TODO add link to docs), which we download to the host if it is not already cached and untar on every job to have a clean state for the emulators to start from. | These AVD definitions are stored on a tar ball which we store on tooltool (TODO add link to docs), which we download to the host if it is not already cached and untar on every job to have a clean state for the emulators to start from. | ||