Issue Type: Bug Bug
Assignee: Jesse Glick
Components: mailer
Created: 04/Dec/13 12:16 PM
Description:

A parallel-capable job was observed to be stuck in a later build just because an earlier build was still running:

"Executor #1 for ... : executing ... #6268 : waiting for Check point mail sent on ... #6266" ...
   java.lang.Thread.State: WAITING (on object monitor)
	at java.lang.Object.wait(Native Method)
	at java.lang.Object.wait(Object.java:503)
	at hudson.model.Run$RunExecution$CheckpointSet.waitForCheckPoint(Run.java:1453)
	- locked <0x...> (a hudson.model.Run$RunExecution$CheckpointSet)
	at hudson.model.Run.waitForCheckpoint(Run.java:1411)
	at hudson.model.CheckPoint.block(CheckPoint.java:144)
	at hudson.tasks.MailSender.findPreviousBuildResult(MailSender.java:144)
	at hudson.tasks.MailSender.getMail(MailSender.java:166)
	at hudson.tasks.MailSender.execute(MailSender.java:100)
	at hudson.tasks.Mailer.perform(Mailer.java:117)

As in JENKINS-16376, this is senseless. If the earlier build is not yet done, it is better to just not report any state transition.

Project: Jenkins
Labels: concurrent-build performance
Priority: Critical Critical
Reporter: Jesse Glick
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/groups/opt_out.

Reply via email to