[JIRA] [build-flow] (JENKINS-13523) Missing option "Add timestamps to the Console Output" (Build Environment)
Richard Cross edited a comment on JENKINS-13523 Missing option "Add timestamps to the Console Output" (Build Environment) Actually, I would argue this is non-trivial. True, the start times of the individual jobs called by Build Flow DSL are recorded elsewhere, but an awful lot can happen either side of the DSL, for example a source checkout, or a bunch of post-build activities. Not having any timestamps in the console output of this kind of job is a major annoyance. Please can you raise the priority? 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/groups/opt_out.
[JIRA] [build-flow] (JENKINS-13523) Missing option "Add timestamps to the Console Output" (Build Environment)
Richard Cross commented on JENKINS-13523 Missing option "Add timestamps to the Console Output" (Build Environment) Actually, I would argue this is non-trivial. True, the start times of the individual jobs called by Build Flow DSL are recorded elsewhere, but an awful lot can happen either side of the DSL, for example a source checkout, or a bunch of post-build activites. Not having any timestamps in the console output of this kind of job is a major annoyance. Please can you raise the priority? 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/groups/opt_out.
[JIRA] [xvfb] (JENKINS-21548) Xvfb failure does not fail build
Richard Cross commented on JENKINS-21548 Xvfb failure does not fail build Thanks for the suggestion; I'll try it out when I'm back in the office. By the way, I only hard coded the display number in this job order to replicate the fault. In our live build jobs of course, the display number is left to auto-select, with a high offset to avoid collisions with other processes that require displays. 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/groups/opt_out.
[JIRA] [xvfb] (JENKINS-21548) Xvfb failure does not fail build
Richard Cross commented on JENKINS-21548 Xvfb failure does not fail build Ok - I've replicated the issue. It happens when Xvfb's lock file is removed, but tge display is still running. 1. Start a display on Jenkins Slave: /usr/bin/Xvfb :1972 -screen 0 1024x768x24 & 2. Remove the corresponding locl file: rm -rf /tmp/.X1972-lock 3. Run a simply Jenkins job that starts Xvfb on display 1972, with a single build task (e.g. a 4. Run build job Build job passes successfully, even though the Xvfb plugin logs an error. Started by user Cross, Richard (Contractor) [EnvInject] - Loading node environment variables. Building remotely on appduvirtual0c9 in workspace /buildstore/jenkins_appduvirtual0c9_slave/workspace/Xvfb_test_failure_scenario Xvfb starting$ /usr/bin/Xvfb :1972 -screen 0 1024x768x24 -fbdir /buildstore/jenkins_appduvirtual0c9_slave/2014-02-03_12-23-504926962666561200040xvfb _XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running Fatal server error: Cannot establish any listening sockets - Make sure an X server isn't already running unlink: No such file or directory unlink failed, Invalid argument[Xvfb_test_failure_scenario] $ /bin/sh -xe /tmp/hudson7411154595497137988.sh + echo This should only run is Xvfb is successful. This should only run is Xvfb is successful. Xvfb stopping Notifying upstream projects of job completion Finished: SUCCESS 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/groups/opt_out.
[JIRA] [xvfb] (JENKINS-21548) Xvfb failure does not fail build
Richard Cross edited a comment on JENKINS-21548 Xvfb failure does not fail build Ok - I've replicated the issue. It happens when Xvfb's lock file is removed, but the display is still running. 1. Start a display on Jenkins Slave: /usr/bin/Xvfb :1972 -screen 0 1024x768x24 & 2. Remove the corresponding lock file: rm -rf /tmp/.X1972-lock 3. Run a simply Jenkins job that starts Xvfb on display 1972, with a single build task (e.g. a 4. Run build job Build job passes successfully, even though the Xvfb plugin logs an error. Started by user Cross, Richard (Contractor) [EnvInject] - Loading node environment variables. Building remotely on appduvirtual0c9 in workspace /buildstore/jenkins_appduvirtual0c9_slave/workspace/Xvfb_test_failure_scenario Xvfb starting$ /usr/bin/Xvfb :1972 -screen 0 1024x768x24 -fbdir /buildstore/jenkins_appduvirtual0c9_slave/2014-02-03_12-23-504926962666561200040xvfb _XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed _XSERVTransMakeAllCOTSServerListeners: server already running Fatal server error: Cannot establish any listening sockets - Make sure an X server isn't already running unlink: No such file or directory unlink failed, Invalid argument[Xvfb_test_failure_scenario] $ /bin/sh -xe /tmp/hudson7411154595497137988.sh + echo This should only run is Xvfb is successful. This should only run is Xvfb is successful. Xvfb stopping Notifying upstream projects of job completion Finished: SUCCESS 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/groups/opt_out.
[JIRA] [xvfb] (JENKINS-21548) Xvfb failure does not fail build
Richard Cross edited a comment on JENKINS-21548 Xvfb failure does not fail build Well, this is embarrassing. I'm having difficulty setting up a test job that replicates the issue. With Xvfb configured and a single, simple shell command as the build task, the build aborts if a display is already taken (I run the same display at the command line. In my example above, the issue I was getting is this: http://www.x.org/wiki/FAQErrorMessages/#index6h2 which is slightly harder to replicate manually. 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/groups/opt_out.
[JIRA] [xvfb] (JENKINS-21548) Xvfb failure does not fail build
Richard Cross commented on JENKINS-21548 Xvfb failure does not fail build Well, this is embarrassing. I'm having difficulty setting up a test job that replicates the issue. With Xvfb configured and a single, simple shell command as the build task, the build aborts if a display is already taken. I need to have a more detailed look at the live build that's failing (it runs a series of Maven build tasks) to see what else in the job produces the output in my original post. 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/groups/opt_out.
[JIRA] [xvfb] (JENKINS-21548) Xvfb failure does not fail build
Richard Cross created JENKINS-21548 Xvfb failure does not fail build Issue Type: Improvement Affects Versions: current Assignee: zregvart Components: xvfb Created: 29/Jan/14 3:00 PM Description: When using the Xvfb plugin, if the plugin fails to establish a connection, then the build should fail, as any tests that depend on an Xvfb display are bound to fail also. Or, at least there should be an option in the advance settings to fail the job if Xvfb fails. Currently, the plugin simply logs an error, and then proceeds with the rest of the build job. 12:28:14 Xvfb starting$ /usr/bin/Xvfb :1958 -screen 0 1024x768x24 -fbdir /buildstore/jenkins_0c9_slave/2014-01-29_12-28-139011048368266724308xvfb 12:28:14 _XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed 12:28:14 _XSERVTransMakeAllCOTSServerListeners: server already running 12:28:14 12:28:14 Fatal server error: 12:28:14 Cannot establish any listening sockets - Make sure an X server isn't already running 12:28:14 unlink: No such file or directory 12:28:14 unlink failed, Invalid argument 12:28:14 ERROR: Xvfb failed to start, consult the lines above for errors 12:28:29 [8mha:WB+LCABb85aBtbiIQSmjNKU4P08vOT+vOD8nVc8DzHWtSE4tKMnMz/PLL0ldFVf2c+b/lb5MDAwVRQxSaBqcITRIIQMEMIIUFgAAckCEiWA= [0mCopied 1 artifact from " [8mha:sB+LCABb85aBtbiIQSajNKU4P08vOT+vOD8nVc+jsiC1KCczL9svvyTVzHb1RttJBUeZGJg8GdhyUvPSSzJ8GJhLi3JKGIR8shLLEvVzEvPS9YNLijLz0q0rihik0IxzhtAgwxgggJGJgaGiAMjQLmEw0M/KT9L3TSwuSS2KL0lNzDUwjHcsLcnPTSxJTYl3K81LLsnMz0vMiQ9JLS4B2qAPABqeEK21AAA [rest of build job proceeds, and inevitably fails] Environment: RHEL 6.2 Project: Jenkins Labels: xvfb Priority: Major Reporter: Richard Cross 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/groups/opt_out.
