[
https://issues.jenkins-ci.org/browse/JENKINS-13556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162296#comment-162296
]
Frank Merrow commented on JENKINS-13556:
----------------------------------------
I have also seen this issue on our Jenkins systems . . .
NOTE: This is NOT a plugin issue . . . this can be duplicated on a "virgin"
Jenkins . . . just fill up all the executors with Jobs and then queue something
so you get the "Waiting for next available executor on ". (Typically means you
had to "node lock" a job.)
Easy to duplicate (for me 100% in 1.459 and 1.460) Never happens on a Jenkins
where none of the jobs are node locked, always happens on Jenkins where the
jobs are node locked. As discussed above, affects both the GUI and the JSON
return values if using Jenkins/Python).
Frank
> Unprintable character in executor name in JSON API output
> ---------------------------------------------------------
>
> Key: JENKINS-13556
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13556
> Project: Jenkins
> Issue Type: Bug
> Components: jenkinswalldisplay
> Affects Versions: current
> Reporter: Chad Myers
>
> After upgrading to the 1.460 version of Jenkins, we noticed that when a build
> was waiting for an executor, if you hovered over the build in the wall
> display, it would say "Waiting for next available executor on
> [ESC][8mha:AAAAiR+LCAAAAAAAAABb85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyT1dMUiOWdZ/mImBiZPBrac1Lz0kgwfBubSopwSBiGfrMSyRP2cxLx0/eCSosy8dOuKIgYpNOOcITTIMAYIYGRiYKgoALFKGLj0k/NzC0pLUov0ATz5UcyPAAAA[ESC][0m"
> The [ESC] was actually the ASCII/ANSI escape character 0x1B.
> When we attempt to use the JSON API to get the status of builds, our script
> (Ruby) fails to parse the JSON due to invalid escape characters in the string:
> "why":"Waiting for next available executor on
> [8mha:AAAAiR+LCAAAAAAAAABb85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyT1dMUiOWdZ/mImBiZPBrac1Lz0kgwfBubSopwSBiGfrMSyRP2cxLx0/eCSosy8dOuKIgYpNOOcITTIMAYIYGRiYKgoALFKGLj0k/NzC0pLUov0ATz5UcyPAAAA[0m"
> Before the [8mha and the [0m there is the invisible 0x1B escape character.
> When we click on the waiting build in the UI to view the build details, it
> says (correctly) "#1849 (pending - Waiting for next available executor on
> master )"
> "master" is the name of our primary build server/executor.
> I have no idea where the big [8mhz:AAAAiR... stuff is coming from.
--
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
