[
https://issues.jenkins-ci.org/browse/JENKINS-13972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163391#comment-163391
]
John Koleszar commented on JENKINS-13972:
-----------------------------------------
I was able to reproduce this by hacking one of Jenkins' unit tests as well:
{noformat}
diff --git
a/test/src/test/groovy/hudson/matrix/MatrixProjectCustomWorkspaceTest.groovy
b/test/src/test/groovy/hudson/matrix/MatrixProjectCustomWorkspaceTest.groovy
index 1ddb195..8b6f324 100644
--- a/test/src/test/groovy/hudson/matrix/MatrixProjectCustomWorkspaceTest.groovy
+++ b/test/src/test/groovy/hudson/matrix/MatrixProjectCustomWorkspaceTest.groovy
@@ -116,7 +116,7 @@ class MatrixProjectCustomWorkspaceTest extends
HudsonTestCase {
*/
def configureCustomWorkspaceConcurrentBuild(MatrixProject p) {
// needs sufficient parallel execution capability
- jenkins.numExecutors = 10
+ jenkins.numExecutors = 4
jenkins.updateComputerList()
p.axes = new AxisList(new TextAxis("foo", "1", "2"))
@@ -140,8 +140,10 @@ class MatrixProjectCustomWorkspaceTest extends
HudsonTestCase {
// get one going
Thread.sleep(1000)
def f2 = p.scheduleBuild2(0)
+ Thread.sleep(1000)
+ def f3 = p.scheduleBuild2(0)
- def bs = [f1, f2]*.get().each { assertBuildStatusSuccess(it) }
+ def bs = [f1, f2, f3]*.get().each { assertBuildStatusSuccess(it) }
return bs
}
}
{noformat}
> Concurrent matrix builds abort
> ------------------------------
>
> Key: JENKINS-13972
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13972
> Project: Jenkins
> Issue Type: Bug
> Components: concurrent-build
> Affects Versions: current
> Reporter: John Koleszar
> Assignee: Kohsuke Kawaguchi
> Priority: Minor
>
> Reproduction case:
> Create a concurrent matrix job with a user defined axis that does a 'sleep
> 120' as its build step. Launch several of these jobs, enough that all
> available executors are taken up and there are still builds in the queue.
> Some of these builds will abort, with a console message similar to:
> [...]
> 9 completed with result SUCCESS
> 24 completed with result SUCCESS
> 23 completed with result SUCCESS
> 2 completed with result SUCCESS
> 10 appears to be cancelled
> 10 completed with result ABORTED
> 25 appears to be cancelled
> 25 completed with result ABORTED
> 18 appears to be cancelled
> 18 completed with result ABORTED
> 13 appears to be cancelled
> [...]
> For my test case, I have 26 slaves, 82 executors, 25 sub-jobs. I can
> reproduce reliably if I launch 5 or more top level jobs at once.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
