[JIRA] [android-emulator] (JENKINS-22334) plugin thinks emulator always crashes using sdk 22.6.1
Christopher Orr closed JENKINS-22334 as Fixed plugin thinks emulator always crashes using sdk 22.6.1 Version 2.11 of the plugin has been released, which fixes this issue. Change By: Christopher Orr (18/May/14 10:20 PM) Status: Open Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-22334) plugin thinks emulator always crashes using sdk 22.6.1
Matthew Zavislak commented on JENKINS-22334 plugin thinks emulator always crashes using sdk 22.6.1 Pauli Kaupppinen (or anyone else) - do you know of a workaround for Gradle builds similar to the one suggested (-Dandroid.device=usb)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-22334) plugin thinks emulator always crashes using sdk 22.6.1
Sam Xiao commented on JENKINS-22334 plugin thinks emulator always crashes using sdk 22.6.1 This becomes a blocker for us, can someone quickly review this and merge it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-22334) plugin thinks emulator always crashes using sdk 22.6.1
Richard Mortimer commented on JENKINS-22334 plugin thinks emulator always crashes using sdk 22.6.1 I have a feeling this is related to the fix to make sure that the Android emulator accepts 5 digit port numbers. https://android-review.googlesource.com/#/c/79532/ That would cause both a localhost and emulator instance to be registered with ADB. This is related to the fix for JENKINS-12821 which only uses the emulator instance. I did experiment with my proposed fix for JENKINS-12821 https://github.com/jenkinsci/android-emulator-plugin/pull/27 to make it register a localhost instance in ADB but that seemed to think that the emulator had crashed. I didn't get chance to explore that further yet. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-22334) plugin thinks emulator always crashes using sdk 22.6.1
Sam Xiao commented on JENKINS-22334 plugin thinks emulator always crashes using sdk 22.6.1 Is JENKINS-22555 related to this? We didn't use Gradle yet, but it seems like very much similar issue. Our tests are start failing since we upgraded our SDK to 22.6.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-22334) plugin thinks emulator always crashes using sdk 22.6.1
Pauli Kaupppinen commented on JENKINS-22334 plugin thinks emulator always crashes using sdk 22.6.1 I have same issue when building android with maven. Jenkins somehow creates localhost and emulator instance even I have one emulator. I did find a workaround for the problem. I defined that android tests should use only usb devive and then only localhost instance is used. That is, I just added –Dandroid.device=usb in maven command and now all works fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-22334) plugin thinks emulator always crashes using sdk 22.6.1
Tom Billiet updated JENKINS-22334 plugin thinks emulator always crashes using sdk 22.6.1 Attached the complete logcat and jenkins output. You'll notice that unit tests are started multiple times as there are several gradle subprojects with tests. Change By: Tom Billiet (25/Mar/14 9:45 AM) Attachment: consoleText Attachment: logcat.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-22334) plugin thinks emulator always crashes using sdk 22.6.1
Christopher Orr commented on JENKINS-22334 plugin thinks emulator always crashes using sdk 22.6.1 Is there a stacktrace in logcat when the app crashes? What is the Jenkins console output for the whole job? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [android-emulator] (JENKINS-22334) plugin thinks emulator always crashes using sdk 22.6.1
Tom Billiet
created JENKINS-22334
plugin thinks emulator always crashes using sdk 22.6.1
Issue Type:
Bug
Affects Versions:
current
Assignee:
Christopher Orr
Components:
android-emulator
Created:
25/Mar/14 9:12 AM
Description:
Running android unit tests from gradle is not possible anymore using the latest android sdk (22.6.1). Using 22.3 everything was fine.
Running the same tests locally without jenkins everything is fine too.
Behavior seen is that the jenkins plugins seems to think that the emulator has crashed and hence stops the tests. Output seen from the gradle script:
Starting 115 tests on sdk - 4.3
com.example.MyTest > testAndroidTestCaseSetupProperly[sdk - 4.3] [31mFAILED [0m
Test failed to run to completion. Reason: 'Instrumentation run failed due to 'Process crashed.''. Check device logcat for details
Tests on sdk - 4.3 failed: Instrumentation run failed due to 'Process crashed.'
Starting 115 tests on emulator-38135 - 4.3
com.example.MyTest > testAndroidTestCaseSetupProperly[emulator-38135 - 4.3] [32mSUCCESS [0m
--> then the tests stop executing. Also strange to notice is that is seems to try to restart a new emulator with the name "emulator-38135" instead of the normal name "sdk"
Logcat output is not very helpful, something seems to force-stop the tests:
03-25 04:12:16.633 I/ActivityManager( 285): Start proc com.mypackage.library.test for added application com.mypackage.library.test: pid=1622 uid=10046 gids={50046, 3003, 1028}
03-25 04:12:17.453 I/TestRunner( 1622): started: testAndroidTestCaseSetupProperly(com.mypackage.MyFirstTest)
03-25 04:12:19.763 I/ActivityManager( 285): Force stopping package com.mypackage.library.test appid=10046 user=0
03-25 04:12:19.763 I/ActivityManager( 285): Killing proc 1622:com.mypackage.library.test/u0a10046: force stop com.mypackage.library.test
03-25 04:12:19.783 W/ActivityManager( 285): Crash of app com.mypackage.library.test running instrumentation ComponentInfo{com.mypackage.library.test.test/android.test.InstrumentationTestRunner}
Project:
Jenkins
Priority:
Critical
Reporter:
Tom Billiet
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
