[Hudson-Issues] [JIRA] Commented: (HUDSON-7354) Emulator interactions when building with configuration grid

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[Hudson-Issues] [JIRA] Commented: (HUDSON-7354) Emulator interactions when building with configuration grid

JIRA issues@hudson.java.net

    [ http://issues.hudson-ci.org/browse/HUDSON-7354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=145678#action_145678 ]

orrc commented on HUDSON-7354:
------------------------------

Hi Matthias,

Does the console output indicate why that particular build always fails?

Regarding the number of builds executed in parallel, that's purely a feature of Hudson.  The job will be split up amongst the currently available executors.  i.e. on the main screen of Hudson, on the left you will see a node called "Master" and executors "1" and "2".

You can configure this in Manage -> Configure to add more or less executors.  The default is two executors per node.  Generally the idea is to add more build slaves to your Hudson cluster, each with one or more executors, to give you more parallel build power.

> Emulator interactions when building with configuration grid
> -----------------------------------------------------------
>
>                 Key: HUDSON-7354
>                 URL: http://issues.hudson-ci.org/browse/HUDSON-7354
>             Project: Hudson
>          Issue Type: Bug
>          Components: android-emulator
>    Affects Versions: current
>         Environment: RHEL 5
> Tomcat 6.0.29
> Hudson 1.374
> ADK tools rev. 6
>            Reporter: jtharp
>            Assignee: orrc
>
> There seem to be interactions between emulators when building on a configuration grid. I have a trivial Android app that I have been using to figure out various build issues, including using Hudson and the Android Plugin.
> I'm sorry that I don't have a completely repeatable sequence that might help in pin-pointing the behavior, but here is the configuration:
> I'm using Hudson's multi-build with two configuration axes: ADK_VER (1.5, 2.1) and SCREEN_RES (HVGA). I have the Android plugin running an emulator with the "Run emulator with properties" option.
> Android OS Version: ${ADK_VER}
> Screen density: 160
> Screen resolution: ${SCREEN_RES}
> Device locale: en_US
> SD card size: {blank}
> Reset emulator state at startup: {unchecked}
> Show emulator window: {unchecked}
> I'm getting fairly regular failures on one of the two builds that result (and more often the second). However, the failure is seldom exactly the same. One time, the build will be unable to connect to the emulator at the beginning and timeout. Another time, one of the builds will be unable to install the apk because it cannot communicate with the target emulator (toward the end of the build and after it had already established a connection with it for an earlier step).
> The problems don't seem to occur when the "Run each configuration sequentially" setting is checked.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.hudson-ci.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira