[JIRA] [android-emulator] (JENKINS-24736) Android emulator plugin does not use all available executors on a slave

[k76...@gmail.com (JIRA)]

JY Hsu created JENKINS-24736 Android emulator plugin does not use all available executors on a slave Issue Type: Bug Assignee: Christopher Orr Components: android-emulator Created: 17/Sep/14 4:23 AM Description: I run android emulator on both Windows 7 and fedora 20 slaves. They all have the problem where the android emulator related job can't utilize all executors on a slave. I configured all jobs to run on specific slaves and slaves to only run jobs specific to that slave. The problem is a little different for launching new emulators versus launching existing emulators. For jobs that creates and launch new emulators, there can only be one of them running on a slave. Any other jobs on the same slave will wait for next executor no matter how many available executors are there on the slave For jobs that launches existing emulators, there seems to be a 7 concurrent jobs limit. I have a very powerful slave machine that I give it 15 executors, and tried to run 10 jobs concurrently. However, only 7 of them were run, and the other 3 were waiting for available executor. Environment: Windows 7 or Fedora 20 Project: Jenkins Priority: Major Reporter: JY Hsu

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.