Daniel Beck commented on Bug JENKINS-24095

Actually it's both not cosmetic (the node will accept a second task) and not a bug (documented to behave this way).

Two issues:

  • Your API doesn't show anything relevant. The second executor will be removed once the task is finished, numExecutors is already 1 before.
  • I've been unable to reproduce the issue if the task executes on the first executor 'executor #0' (see also /threadDump), only if it's a higher index. Hence the recent questions.
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.

Reply via email to