Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: android-emulator-plugin
-
Labels:None
-
Environment:jenkins 1.432-SNAPSHOT with android-emulator 1.19-SNAPSHOT
Slave/Emulator running on Windows 7
-
Similar Issues:
Description
I am seeing frequent emulator startup timeouts on Windows 7. These typically occur on moderately loaded Windows 7 machines when running matrix builds with 2 emulators/slaves running simultaneously.
These are typical values that I am seeing (after raising the existing timeouts).
[android] Emulator is ready for use (took 123 seconds)
[android] Emulator is ready for use (took 103 seconds)
[android] Emulator is ready for use (took 126 seconds)
[android] Emulator is ready for use (took 99 seconds)
[android] Emulator is ready for use (took 105 seconds)
[android] Emulator is ready for use (took 133 seconds)
[android] Emulator is ready for use (took 135 seconds)
[android] Emulator is ready for use (took 84 seconds)
[android] Emulator is ready for use (took 123 seconds)
[android] Emulator is ready for use (took 103 seconds)
[android] Emulator is ready for use (took 126 seconds)
[android] Emulator is ready for use (took 99 seconds)
[android] Emulator is ready for use (took 105 seconds)
[android] Emulator is ready for use (took 133 seconds)
The highest time I recorded was 143 seconds.
As a minimum timeout needs to raised to 180 seconds or so.
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Workflow | JNJira [ 141224 ] | JNJira + In-Review [ 205326 ] |
Integrated in
plugins_android-emulator #24
[FIXED JENKINS-11014] Increased startup timeout to 180 seconds.
Christopher Orr :
Files :