|
||||||||
|
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.
If multiple jobs try to use the same existing named emulator on the same slave, only one build can use the emulator at at time, blocking the other builds.
If two jobs have the same emulator properties, the same will happen.
What do your 10 jobs look like? Are they 10 separate Jenkins jobs, or are you trying to run multiple builds of the same job? Do they all have completely unique OS/density/resolution/locale/ABI?