-
Bug
-
Resolution: Fixed
-
Major
-
Linux master and slaves, slaves run via ssh
Since having updated Jenkins to 1.481 and the Warnings Plugin to 4.16 (and subsequently to 4.17), I get the following errors in some of the jobs:
ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception java.lang.NullPointerException at hudson.plugins.warnings.WarningsResult.getFileName(WarningsResult.java:108) at hudson.plugins.warnings.WarningsResult.getSerializationFileName(WarningsResult.java:94) at hudson.plugins.analysis.core.BuildResult.getDataFile(BuildResult.java:481) at hudson.plugins.analysis.core.BuildResult.loadResult(BuildResult.java:896) at hudson.plugins.analysis.core.BuildResult.getProject(BuildResult.java:880) at hudson.plugins.analysis.core.BuildResult.getContainer(BuildResult.java:1020) at hudson.plugins.analysis.core.BuildResult.getAnnotations(BuildResult.java:563) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:238) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:289) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1527) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236)
An example is this job: http://espressomd.org/jenkins/job/ESPResSo-nightly-distcheck/
I have attached a tarfile of the whole job directory (without the artifacts), so that you can check for yourself.
Here is some more information:
- The error is reproducible when running the job again.
- After the discussion in the plugin's comment section, I have checked the contents of the job directory.
- Build 224 has a file build.xml that contains three <result class="hudson.plugins.warnings.WarningsResult"> tags, but all of them have a <group> subtag and the corresponding *-warnings.xml-file. The log contains the error.
- The build before ran without any trouble. Its build.xml does not contain any WarningResult tag, as the plugin was deactivated during that time.
- All other builds before either contained one (or more) files compiler-warnings.xml and the corresponding sections in build.xml.
[JENKINS-15413] NPE - compiler-warnings.xml not found
Description |
Original:
Since having updated Jenkins to 1.481 and the Warnings Plugin to 1.416 (and subsequently to 1.417), I get the following errors in some of the jobs: {noformat} ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception java.lang.NullPointerException at hudson.plugins.warnings.WarningsResult.getFileName(WarningsResult.java:108) at hudson.plugins.warnings.WarningsResult.getSerializationFileName(WarningsResult.java:94) at hudson.plugins.analysis.core.BuildResult.getDataFile(BuildResult.java:481) at hudson.plugins.analysis.core.BuildResult.loadResult(BuildResult.java:896) at hudson.plugins.analysis.core.BuildResult.getProject(BuildResult.java:880) at hudson.plugins.analysis.core.BuildResult.getContainer(BuildResult.java:1020) at hudson.plugins.analysis.core.BuildResult.getAnnotations(BuildResult.java:563) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:238) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:289) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1527) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) {noformat} An example is this job: [http://espressomd.org/jenkins/job/ESPResSo-nightly-distcheck/] I have attached a tarfile of the whole job directory (without the artifacts), so that you can check for yourself. Here is some more information: * The error is reproducible when running the job again. * After the discussion in the plugin's comment section, I have checked the contents of the job directory. ** Build 224 has a file {{build.xml}} that contains three {{<result class="hudson.plugins.warnings.WarningsResult">}} tags, but all of them have a {{<group>}} subtag and the corresponding {{*-warnings.xml}}-file. The log contains the error. ** The build before ran without any trouble. Its {{build.xml}} does not contain any {{WarningResult}} tag, as the plugin was deactivated during that time. ** All other builds before either contained one (or more) files {{compiler-warnings.xml}} and the corresponding sections in {{build.xml}}. |
New:
Since having updated Jenkins to 1.481 and the Warnings Plugin to 4.16 (and subsequently to 4.17), I get the following errors in some of the jobs: {noformat} ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception java.lang.NullPointerException at hudson.plugins.warnings.WarningsResult.getFileName(WarningsResult.java:108) at hudson.plugins.warnings.WarningsResult.getSerializationFileName(WarningsResult.java:94) at hudson.plugins.analysis.core.BuildResult.getDataFile(BuildResult.java:481) at hudson.plugins.analysis.core.BuildResult.loadResult(BuildResult.java:896) at hudson.plugins.analysis.core.BuildResult.getProject(BuildResult.java:880) at hudson.plugins.analysis.core.BuildResult.getContainer(BuildResult.java:1020) at hudson.plugins.analysis.core.BuildResult.getAnnotations(BuildResult.java:563) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:238) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:289) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1527) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) {noformat} An example is this job: [http://espressomd.org/jenkins/job/ESPResSo-nightly-distcheck/] I have attached a tarfile of the whole job directory (without the artifacts), so that you can check for yourself. Here is some more information: * The error is reproducible when running the job again. * After the discussion in the plugin's comment section, I have checked the contents of the job directory. ** Build 224 has a file {{build.xml}} that contains three {{<result class="hudson.plugins.warnings.WarningsResult">}} tags, but all of them have a {{<group>}} subtag and the corresponding {{*-warnings.xml}}-file. The log contains the error. ** The build before ran without any trouble. Its {{build.xml}} does not contain any {{WarningResult}} tag, as the plugin was deactivated during that time. ** All other builds before either contained one (or more) files {{compiler-warnings.xml}} and the corresponding sections in {{build.xml}}. |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 146147 ] | New: JNJira + In-Review [ 191797 ] |
This seems to be the same bug as
JENKINS-15017, i.e. apparently it is a duplicate. I'm not sure whether it is the same asJENKINS-14989, though, as the stack trace is not the same. Could be different versions of the plugin, though.