[
https://issues.jenkins-ci.org/browse/JENKINS-10468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161967#comment-161967
]
Frank Merrow edited comment on JENKINS-10468 at 4/24/12 4:39 PM:
-----------------------------------------------------------------
Odd to find this problem being so old, but I have some updates which might
apply here . . .
I see this issue as described above in 1.458. However, I also have two systems
one at 1.459 and one at 1.460 . . . in both these systems, when I mouse over a
pending job that is waiting for an executor I see "Waiting for next available
executor on <line noise>". (Line Noise == Huge long string of random
characters that fills the screen to the right.)
Note that whatever this issue is, it is not isolated to the GUI. Both those
systems, ONLY when there is a job waiting for a specific system, the JSON
returned from a python/jenkins get_queue_info() returns as "malformed" error .
. . I debugged into the JSON and see this exact same message (with line noise)
shown in the malformed JSON packet . . . at exactly the place in the JSON that
the error message said was malformed.
Like I say, for both the GUI and the JSON . . . this only happens when a job is
waiting for a specific system . . . other types of jobs do no cause this
problem. Unfortunately, we have a fair percentage of these on some systems.
I down graded the machine at 1.460 to 1.458 . . . now JSON works, but as noted
above, the system name is now not shown . . . I'm guessing in one version you
got lucky and are pointing at zero to terminate the string, but in the next two
version you just happened to point at active data.
NOTE: I find this very easy to duplicate on my systems:
1. fill up all executors with any job (my favorite is sleep 1000000)
2. now queue any job that requires a specific system to run . . .
3. wait 15 seconds, then mouse over the waiting job.
Frank
P.S. This problem will duplicate as described even if ALL PLUGINS are disabled
. . . it is not a plugin issue . . . at least not in 1.459 and/or 1.460 . . .
was (Author: fmerrow):
Odd to find this problem being so old, but I have some updates which might
apply here . . .
I see this issue as described above in 1.458. However, I also have two systems
one at 1.459 and one at 1.460 . . . in both these systems, when I mouse over a
pending job that is waiting for an executor I see "Waiting for next available
executor on <line noise>". (Line Noise == Huge long string of random
characters that fills the screen to the right.)
Note that whatever this issue is, it is not isolated to the GUI. Both those
systems, ONLY when there is a job waiting for a specific system, the JSON
returned from a python/jenkins get_queue_info() returns as "malformed" error .
. . I debugged into the JSON and see this exact same message (with line noise)
shown in the malformed JSON packet . . . at exactly the place in the JSON that
the error message said was malformed.
Like I say, for both the GUI and the JSON . . . this only happens when a job is
waiting for a specific system . . . other types of jobs do no cause this
problem. Unfortunately, we have a fair percentage of these on some systems.
I down graded the machine at 1.460 to 1.458 . . . now JSON works, but as noted
above, the system name is now not shown . . . I'm guessing in one version you
got lucky and are pointing at zero to terminate the string, but in the next two
version you just happened to point at active data.
NOTE: I find this very easy to duplicate on my systems:
1. fill up all executors with any job (my favorite is sleep 1000000)
2. now queue any job that requires a specific system to run . . .
3. wait 15 seconds, then mouse over the waiting job.
Frank
> 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
