Closed Bug 1117954 Opened 11 years ago Closed 11 years ago

Running Mozharness for Android can fail too late due to having the wrong SDK

Categories

(Release Engineering :: Applications: MozharnessCore, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: armenzg, Unassigned)

Details

gbrown, jlund: which SDK is needed to run the API 11 jobs? And is it api 10 or api 11? FTP vs treeherder naming is confusing me. I also updated https://wiki.mozilla.org/ReleaseEngineering/Platforms/Android a bit. 15:32:37 INFO - Calling ['adb', '-s', 'emulator-5554', 'install', '-r', '/home/armenzg/repos/mozharness/build/fennec-37.0a1.en-US.android-arm.apk'] with output_timeout 300 15:32:46 INFO - 4269 KB/s (38308825 bytes in 8.763s) 15:32:47 INFO - pkg: /data/local/tmp/fennec-37.0a1.en-US.android-arm.apk 15:32:49 ERROR - Failure [INSTALL_FAILED_OLDER_SDK] python scripts/android_emulator_unittest.py --cfg android/androidarm.py --test-suite mochitest-gl-1 --blob-upload-branch try --download-symbols ondemand --cfg developer_config.py --installer-url http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-central-android-api-11/en-US/fennec-37.0a1.en-US.android-arm.apk --test-url http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-mozilla-central-android-api-11/en-US/fennec-37.0a1.en-US.android-arm.tests.zip
The apk associated with treeherder "Android 4.0 API10+" jobs requires SDK api 11 (Android 3.0).
(In reply to Geoff Brown [:gbrown] from comment #1) > The apk associated with treeherder "Android 4.0 API10+" jobs requires SDK > api 11 (Android 3.0). How can we check that the right SDK is installed? It seems that we need to check for it. In order to install the API 11 this is what I did: * sudo apt-get install default-jre (since I did not have java) * dist/android-sdk-linux/tools/android sdk * I left selected the packages that it had selected for me * selected "Android 3.0 (API 11)" and installed all of them ** it takes few minutes Is it good enough by checking under here: armenzg@armenzg-thinkpad:~/dist/android-sdk-linux$ ls -la platforms total 16 drwxrwxr-x 4 armenzg armenzg 4096 Jan 6 12:47 . drwxrwxr-x 13 armenzg armenzg 4096 Jan 6 12:03 .. drwxrwxr-x 7 armenzg armenzg 4096 Jan 6 12:47 android-11 drwxrwxr-x 5 armenzg armenzg 4096 Jan 6 12:00 android-21 Even after I installed it I get this error: armenzg@armenzg-thinkpad:~/repos/mozharness$ adb -s emulator-5554 install -r /home/armenzg/repos/mozharness/build/fennec-37.0a1.en-US.android-arm.apk 4025 KB/s (38338189 bytes in 9.301s) pkg: /data/local/tmp/fennec-37.0a1.en-US.android-arm.apk Failure [INSTALL_FAILED_OLDER_SDK]
INSTALL_FAILED_OLDER_SDK is not complaining about the sdk installed on the host, but rather is complaining about the version of Android installed on the device or emulator. The build associated with "Android 4.0 API10+" can only be installed on a device running Android 3.0 or higher -- it cannot run on the Android 2.3 emulator.
What?! I just realized that those jobs are being run by pandas. Are there any plans to move Android 4.0 jobs to the cloud or iX machines? What was again the value we gain from running on the pandas? I've lost context after such a long time! For giggles, how could I select a 4.0 emulator? Do I need different AVDs?
I'm trying to get an Android 4.4 emulator running this quarter - bug 1062365 - but currently we don't run any tests against the arm emulator except Android 2.3. Emulators don't emulate everything and the pandas have been good to us, so I see value there, but there has been talk of retiring them. I don't know specifics. You would need different avds. You can create a 4.0 (or whatever version you like) avd easily enough and run tests via adb, but to run with sut it gets trickier. I've described some steps in bug 1062365 but don't have that completely worked out yet.
Thanks a lot for explaining this to me! As it is, there's no issue in here but a misunderstanding of what I was trying to run.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.