[
https://issues.jenkins-ci.org/browse/JENKINS-10468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162474#comment-162474
]
Fred G commented on JENKINS-10468:
----------------------------------
The huge long string of random characters that Frank describes is probably
caused by my recent commit:
https://github.com/jenkinsci/jenkins/commit/ff4b02559534c4c67ef95a13defcd7a4fc850a1b
I already opened up a pull request to fix this issue. Sorry for the
inconveniences caused.
> Build Queue does not show the executor a build is waiting for
> -------------------------------------------------------------
>
> Key: JENKINS-10468
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10468
> Project: Jenkins
> Issue Type: Bug
> Components: core, gui
> Environment: Jenkins 1.420 on Windows 2003 Server
> Reporter: Martin Ba
> Priority: Minor
>
> I have a Job bound to master. This job has been started by a script and is
> now waiting for execution on master because another Job is running on the
> master (one executor).
> The Build Queue mouseover displays: "Waiting for next available executor on"
> (*no* mention of which node)
> The Build Queue xml api shows:
> {noformat}
> <queue>
> <item>
> <action>
> <cause>
> <shortDescription>Started by remote host
> 127.0.0.1 with note: server_post_promote transaction -snip- / 169402 @
> 2011/07/27 13:10:03</shortDescription>
> </cause>
> <cause>
> <shortDescription>Started by remote host
> 127.0.0.1 with note: server_post_promote transaction -snip- / 169419 @
> 2011/07/27 13:21:18</shortDescription>
> </cause>
> </action>
> <blocked>false</blocked>
> <buildable>true</buildable>
> <params></params>
> <stuck>true</stuck>
> <task>
> <name>BS-Update-1</name>
> <url>http://-snip-/jenkins/job/BS-Update-1/</url>
> <color>blue</color>
> </task>
> <why>Waiting for next available executor on </why>
>
> <buildableStartMilliseconds>1311772204293</buildableStartMilliseconds>
> </item>
> </queue>
> {noformat}
> Note how the _why_ is missing the node name.
> Going to the job page however, the Build history is (correctly) displaying:
> "#24 (pending - Waiting for next available executor on master )"
> I have also cross-checked with another job that is also bound to master:
> When I start it manually, the same problem exists wrt. to the non-displayed
> node name.
> (And I assume that the fact that this job is display as "stuck" whereas the
> manually started one isn't, is just to do with how "stuck" is calculated and
> that this job has waited more often or something.)
--
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
