[
https://issues.apache.org/jira/browse/CB-11016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard B Knoll resolved CB-11016.
----------------------------------
Resolution: Not A Problem
We removed the Android Windows CI builder from medic and Jenkins
> Android Emulator in WIndows has some issues in CI
> -------------------------------------------------
>
> Key: CB-11016
> URL: https://issues.apache.org/jira/browse/CB-11016
> Project: Apache Cordova
> Issue Type: Test
> Components: Medic
> Reporter: Sarangan Rajamanickam
> Assignee: Richard B Knoll
> Labels: android, found-by-ci, triaged
>
> Two problems that result in run failures:
> 1. The app fails to run for some reason. For this failure we do actually get
> logcat output and this appears (though I am unsure if it is the root cause):
> {noformat}
> D/asset ( 371): failed to open Zip archive
> '/data/app/org.apache.mobilespec-1.apk'
> W/PackageParser( 371): Unable to read AndroidManifest.xml of
> /data/app/org.apache.mobilespec-1.apk
> W/PackageParser( 371): java.io.FileNotFoundException: AndroidManifest.xml
> W/PackageParser( 371): at
> android.content.res.AssetManager.openXmlAssetNative(Native Method)
> W/PackageParser( 371): at
> android.content.res.AssetManager.openXmlBlockAsset(AssetManager.java:488)
> W/PackageParser( 371): at
> android.content.res.AssetManager.openXmlResourceParser(AssetManager.java:456)
> W/PackageParser( 371): at
> android.content.pm.PackageParser.parsePackage(PackageParser.java:528)
> W/PackageParser( 371): at
> com.android.server.pm.PackageManagerService.scanPackageLI(PackageManagerService.java:3569)
> W/PackageParser( 371): at
> com.android.server.pm.PackageManagerService.scanDirLI(PackageManagerService.java:3492)
> W/PackageParser( 371): at
> com.android.server.pm.PackageManagerService.<init>(PackageManagerService.java:1383)
> W/PackageParser( 371): at
> com.android.server.pm.PackageManagerService.main(PackageManagerService.java:1042)
> W/PackageParser( 371): at
> com.android.server.ServerThread.initAndLoop(SystemServer.java:241)
> W/PackageParser( 371): at
> com.android.server.SystemServer.main(SystemServer.java:1179)
> W/PackageParser( 371): at java.lang.reflect.Method.invokeNative(Native
> Method)
> W/PackageParser( 371): at
> java.lang.reflect.Method.invoke(Method.java:515)
> W/PackageParser( 371): at
> com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:785)
> W/PackageParser( 371): at
> com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601)
> W/PackageParser( 371): at dalvik.system.NativeStart.main(Native Method)
> {noformat}
> 2. The emulator goes offline. In this case we fail to deploy the app and
> logcat fails as well
> This log appears in the medic-run step
> {noformat}
> [MEDIC LOG Wed, 06 Apr 2016 19:15:47 GMT] no device found, so switching to
> emulator
> [MEDIC LOG Wed, 06 Apr 2016 19:15:47 GMT] Attempting to start Android emulator
> Error: Failed to deploy to device, no devices found.
> {noformat}
> And this one appears in the medic-log step:
> {noformat}
> [MEDIC LOG Wed, 06 Apr 2016 19:40:48 GMT] running:
> [MEDIC LOG Wed, 06 Apr 2016 19:40:48 GMT] adb devices
> List of devices attached
> emulator-5554 offline
> [MEDIC LOG Wed, 06 Apr 2016 19:40:48 GMT] running:
> [MEDIC LOG Wed, 06 Apr 2016 19:40:48 GMT] adb logcat -d
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
