ReleaseEngineering/Platforms/Android: Difference between revisions

ReleaseEngineering/Platforms/Android (view source)

6 bytes removed , 11 February 2014

Confirmed users

3,990

edits

@@ Line 75: / Line 75: @@
 == Emulator parallelization ==
-For the Android 2.3 and Android x86 jobs we're using emulator and use multiple ones at a time.
+The Android x86 jobs run inside Android emulators. Android 2.3 only triggers one emulator since it runs on single-core machines.
-Mozharness starts up four Android emulators run on each emulator a different test suite.
+Mozharness starts up Android emulators for each 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.
+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 installed.
-These AVD definitions are stored on a tar ball, which we store on ToolTool, which we download to the host if
+These AVD definitions are stored on a tar ball, which we store on ToolTool. We download  the AVD definitions to the host if
 it is not already cached. We untar it 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 u
 = Artifacts =