![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
Unassigned |
|
Components:
|
multijob-plugin |
|
Created:
|
11/Mar/15 7:41 PM
|
|
Description:
|
With a job configuration like:
parent_job:
child_job
child_job
occasionally we'll get output that looks like this:
Starting build job child_job.
Starting build job child_job.
Finished Build : #123 - Job : child_job with status : SUCCESS
<this hangs forever, so we abort the parent_job>
Aborting all subjobs.
Finished Build : #124 - Job : child_job with status : ABORTED
However, job #124 will always have finished successfully. We see this relatively rarely (~5% of parent_job builds?). My guess is that there's a race condition causing this, since we usually see this during times of high load (ie many child_job instances are being started).
|
|
Environment:
|
jenkins 1.593
multijob plugin 1.16
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Simon Weber
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/d/optout.
