1122317 - Deploy Android sdk r24.0.2 on Android emulator test slaves

Status: RESOLVED INVALID

(Infrastructure & Operations Graveyard :: CIDuty, task, P2)

Description

[Geoff Brown [:gbrown]]

+++ This bug was initially created as a clone of Bug #933918 +++

The Firefox for Android team wants to run unit tests in automation against Android 4.4 emulators; I'm sorting out how to do that in bug 1062365.

To run an emulated Android 4.4 environment, Android SDK Tools 22.3 or higher is recommended, and in fact, seems necessary. Our existing Android-x86 4.2 and Android-armv7 2.3 test environments use the emulator from /tools/android-sdk18, which we last modified in bug 933918, with a special patched emulator based on Android SDK Tools 22.0.5 -- just a little too old!

I think we should keep using /tools/android-sdk18 for our existing Android emulator tests, but I would like to have a /tools/android-sdk24 deployed, so that we can run Android 4.4 emulator tests.

We can populate /tools/android-sdk24 from http://dl.google.com/android/android-sdk_r24.0.2-linux.tgz -- the latest SDK-only download available today.


We are several steps away from running Android 4.4 emulator tests in continuous integration, but this change would be beneficial to me now: I have tested locally and want to see how the 4.4 emulator behaves on aws. I have tried running on try against my own mozharness with 4.4 avds, but that fails because I am picking up the android-sdk18 emulator, and that fails to start:

https://treeherder.mozilla.org/#/jobs?repo=try&revision=2dd6e650c2fc

Comment 1

[Geoff Brown [:gbrown]]

On irc, :armenzg suggested going about this a little differently: enhance the mozharness script, android_emulator_unittest.py, to install the needed sdk from tooltool, if not found. That would have advantages:
 - when running outside of a production environment (developer mode) the script can setup the sdk -- no need for the developer to go through an additional step
 - for bug 1062365, I can configure the tooltool fetch to get the sdk from my own tooltool repo, so we would not need to deploy anything right now.

I think I'll investigate that approach.