[JIRA] (JENKINS-57912) Jenkins build fail with emulator issue

4 views
Skip to first unread message

ishank@lightwavetechnology.com (JIRA)

unread,
Jun 7, 2019, 9:41:03 AM6/7/19
to jenkinsc...@googlegroups.com
Ishan Kansara created an issue
 
Jenkins / Bug JENKINS-57912
Jenkins build fail with emulator issue
Issue Type: Bug Bug
Assignee: Christopher Orr
Components: android-emulator-plugin
Created: 2019-06-07 13:40
Environment: Jenkins version: 2.164.1
OS : Windows 10
Android emulator plugin : 3.0
JDK: 1.8.0
Browser: Chrome
Labels: jenkins plugin windows
Priority: Major Major
Reporter: Ishan Kansara

 

//  > git rev-parse "refs/remotes/origin/jenkins^{commit}" # timeout=10
 > git rev-parse "refs/remotes/origin/refs/heads/jenkins^{commit}" # timeout=10
Checking out Revision 180d412c0dbee298a137ae1635b7269874cc5fdb (refs/remotes/origin/jenkins)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 180d412c0dbee298a137ae1635b7269874cc5fdb
Commit message: "Update gradle.properties"
 > git rev-list --no-walk af1a52e8b891ee5d47b407a6bef5e75bb790d336 # timeout=10
No emails were triggered.
$ C:\Users\ishan\AppData\Local\Android\/tools/bin/avdmanager.bat list target
[android] Using Android SDK: C:\Users\ishan\AppData\Local\Android\
[android] Waiting 5 seconds before starting emulator...
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe start-server
* daemon not running; starting now at tcp:5863
* daemon started successfully
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe start-server
[android] Snapshots are enabled, but cannot be used as they are not supported by the current SDK Tools
[android] Starting Android emulator
[android] Erasing existing emulator data...
$ C:\Users\ishan\AppData\Local\Android\/emulator/emulator.exe -ports 5740,5741 -report-console tcp:5810,max=60 -avd My_Nexus -wipe-data
HAX is working and emulator runs in fast virt mode.
dsound: Could not initialize DirectSoundCapture
dsound: Reason: No sound driver is available for use, or the given GUID is not a valid DirectSound device ID
dsound: Attempt to initialize voice without DirectSoundCapture object
dsound: Attempt to initialize voice without DirectSoundCapture object
audio: Failed to create voice `goldfish_audio_in'
C:\Users\ishan\AppData\Local\Android\emulator\qemu\windows-x86_64\qemu-system-i386.exe: warning: opening audio input failed
emulator: WARNING: Requested adb port (5741) is outside the recommended range [5555,5586]. ADB may not function properly for the emulator. See -help-port for details.
[android] Emulator reported that the console is available on port 5,740
[android] Waiting for emulator to finish booting...
dsound: Attempt to initialize voice without DirectSoundCapture object
dsound: Attempt to initialize voice without DirectSoundCapture object
audio: Failed to create voice `adc'
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
Your emulator is out of date, please update by launching Android Studio:
 - Start Android Studio
 - Select menu "Tools > Android > SDK Manager"
 - Click "SDK Tools" tab
 - Check "Android Emulator" checkbox
 - Click "OK"emulator: INFO: boot completed
emulator: INFO: boot time 71318 ms
emulator: Increasing screen off timeout, logcat buffer size to 2M.
emulator: Revoking microphone permissions for Google App.
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete
[android] Timed-out after waiting 720 seconds for emulator
[android] Stopping Android emulator
emulator: Saving state on exit with session uptime 730231 ms
$ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe kill-server
Email was triggered for: Always
Sending email for trigger: Always
Sending email to: Ish...@lightwavetechnology.com
Finished: NOT_BUILT

Jenkins build fails due to emulator issue: $ C:\Users\ishan\AppData\Local\Android\/platform-tools/adb.exe -s emulator-5740 wait-for-device shell getprop dev.bootcomplete

 

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

Dragana.Stojanovikj@payten.com (JIRA)

unread,
Nov 19, 2019, 3:39:06 AM11/19/19
to jenkinsc...@googlegroups.com
Dragana Stojanovikj commented on Bug JENKINS-57912
 
Re: Jenkins build fail with emulator issue

Same happens to me on CentOS 6.5

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

Dragana.Stojanovikj@payten.com (JIRA)

unread,
Nov 20, 2019, 3:39:03 AM11/20/19
to jenkinsc...@googlegroups.com
Dragana Stojanovikj updated an issue
 
Change By: Dragana Stojanovikj
Comment:
Same happens to me on CentOS 6.5
Reply all
Reply to author
Forward
0 new messages