1170227 - Android 4.3 emulator intermittently fails during tests

Status: RESOLVED WONTFIX

(Testing :: General, defect)

Description

[Geoff Brown [:gbrown]]

In bugs like 1157948, tests running on Android 4.3 intermittently fail with communication errors - attempts to retrieve logs or status from the emulator over adb suddenly fail.

After the failure, stop-emulator diagnostics typically look like this:

04:23:34     INFO - #####
04:23:34     INFO - ##### Running stop-emulator step.
04:23:34     INFO - #####
04:23:34     INFO - Running pre-action listener: _resource_record_pre_action
04:23:34     INFO - Running main action method: stop_emulator
04:23:34     INFO - Verifying adb connectivity
04:23:34     INFO - Running timeout 300 /builds/slave/test/build/android-sdk18/platform-tools/adb wait-for-device
04:28:34     INFO - Running timeout 300 /builds/slave/test/build/android-sdk18/platform-tools/adb devices
04:28:34     INFO - List of devices attached
04:28:34  WARNING - Unable to communicate with emulator via adb
04:28:34     INFO - Let's kill every process called emulator64-arm
04:28:34     INFO - Killing pid 1664.

Note that the emulator is running, but adb does not see it.

Comment 1

[Geoff Brown [:gbrown]]

We currently use adb from the android api 18 sdk. I tried upgrading to android api 22 (adb 1.0.32), but continued to see failures just like in bug 1157948.

Comment 2

[Geoff Brown [:gbrown]]

If we can't find a way to fix this, I wonder if the failure message can be manipulated to be more descriptive and/or translate the orange into a blue (retry).

Comment 3

[Geoff Brown [:gbrown]]

This still happens but now cause retries.

Comment 4

[Geoff Brown [:gbrown]]

These continue to occur on a low-frequency basis and are handled as retries.

Comment 5

[Geoff Brown [:gbrown]]

(In reply to Geoff Brown [:gbrown] from comment #4)
> These continue to occur on a low-frequency basis and are handled as retries.

Still true, but I don't think there is any other actionable work here.