[JIRA] (JENKINS-13915) NPE Exception, possibly caused by disabled jobs?

[bgold...@synopsys.com (JIRA)]

Ben Golding commented on JENKINS-13915 NPE Exception, possibly caused by disabled jobs? I could reproduce this issue again today. In this case the assigned node for *_de02winterm20 jobs was disconnected (JNLP slave was not running). Notice from the log below, two *_de02winterm20 jobs are triggered but do not complete: =========== parallel { Trigger job rsync_binmod_de02winterm31 Trigger job rsync_binmod_stormcs241 Trigger job downmerge_f2011.06 Trigger job rsync_SDR_de02winterm31 Trigger job rsync_SDR_stormcs240 Trigger job rsync_SDR_stormcs241 Trigger job rsync_binmod_de02winterm20 Trigger job checkbinmod Trigger job rsync_binmod_stormcs240 Trigger job downmerge_main Trigger job rsync_SDR_de02winterm20 Trigger job downmerge_g2012.06 Trigger job removebinmod checkbinmod #68 completed downmerge_main #143 completed downmerge_f2011.06 #124 completed rsync_binmod_stormcs240 #47 completed removebinmod #66 completed rsync_binmod_stormcs241 #350 completed rsync_binmod_de02winterm31 #40 completed rsync_SDR_de02winterm31 #39 completed rsync_SDR_stormcs240 #42 completed rsync_SDR_stormcs241 #122 completed downmerge_g2012.06 #93 completed FATAL: null java.lang.NullPointerException at org.codehaus.groovy.runtime.callsite.GetEffectivePojoPropertySite.acceptGetProperty(GetEffectivePojoPropertySite.java:51) [... see attached console.log for full backtrace ...]

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