[JIRA] (JENKINS-14135) NPE

Carsten Otto created JENKINS-14135

NPE

Issue Type:	Bug
Assignee:	npiguet
Components:	sloccount
Created:	18/Jun/12 9:13 PM
Description:	This happens with 1.8. I get the sloccount-data (report.sc) and some other XML files (findbugs etc.). Other than that, the workspace is empty. After retrieving the files, I run the publishers. Please tell me how to work around this issue or fix the plugin. If you need more information, please ask. I'm not sure how to write bug reports in here. Best regards, Carsten ERROR: Publisher hudson.plugins.sloccount.SloccountPublisher aborted due to exception java.lang.NullPointerException at hudson.plugins.sloccount.model.SloccountParser.parseLine(SloccountParser.java:92) at hudson.plugins.sloccount.model.SloccountParser.parse(SloccountParser.java:59) at hudson.plugins.sloccount.model.SloccountParser.parse(SloccountParser.java:50) at hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:40) at hudson.plugins.sloccount.model.SloccountParser.invoke(SloccountParser.java:17) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2180) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:722)
Project:	Jenkins
Priority:	Major
Reporter:	Carsten Otto

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

Joe Hansche assigned JENKINS-14135 to sogabe

NPE

Same error, same version. Running Jenkins version 1.470. Reassigning to Seiji, since Nicolas appears to have not been involved in the project since roughly 2009.
Change By:	Joe Hansche (20/Jun/12 7:19 PM)
Assignee:	npiguet sogabe

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

Karsten Brandt assigned JENKINS-14135 to Karsten Brandt

NPE

Change By:	Karsten Brandt (28/Jun/12 5:51 PM)
Assignee:	sogabe Karsten Brandt

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

Karsten Brandt commented on JENKINS-14135

NPE

I've created a similar test environment. But I wasn't able to reproduce this reported error. Therefore, I need more information. 1.) jenkins server environment: WINDOWS or UNIX/LINUX ? 2.) detailed configuration settings, especially the search pattern for your sloccount input file 3.) Please send us a example of a workspace, which leads to this error. This will be very useful. Then I will fix this error as soon as possible. Regards, kbrandt

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

Carsten Otto commented on JENKINS-14135

NPE

1) Linux. 2) dist/report.sc 3) http://aprove.informatik.rwth-aachen.de/~cotto/workspace.zip (I deleted everything but the dist/ directory. If you need more, we need to fine tune - I cannot give you the source of our project.)

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

Carsten Otto commented on JENKINS-14135

NPE

What kind of details reg. 2 do you need?

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

Karsten Brandt commented on JENKINS-14135

NPE

Hello Carsten, I've repeated my tests with your workspace, but there is also no error occurred. All looks fine and no error message pops up. Please, could you try to remove all files from your workspace (step by step) until this error will not occur any more? Or vice versa, start with an empty workspace (only your result.sc should be there) and then add file by file to your workspace. If you have find the culprit, you can send him to us. So we can improve the robustness of this plugin. In case of non success the failure seems to be in your environment. Then send us detailed information like version of used jenkins server, installed plugins (with version information) and so on. Have you tried this also with sloccount plugin version 1.7? Good luck, Karsten

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

Carsten Otto commented on JENKINS-14135

NPE

It works with 1.7. Can you tell me how I can manually test this? I have no idea how to remove files from my workspace after a build and before running the plugin. Some way to test this in my shell would be nice.

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

Karsten Brandt commented on JENKINS-14135

NPE

Copy your sloccount output file into a separate folder and set your workspace accordingly. For example: The new created folder is: /tmp/jenkins_test And the complete path to the sloccount file is: /tmp/jenkins_test/result.sc Set your workspace to: /tmp/jenkins_test Your test job should have no build actions. Only the sloccount output file shall be processed! Therefore, don't forget to set the search pattern for the sloccount file accordingly. Now, you should have a clean test environment...

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

 

Karsten Brandt edited a comment on JENKINS-14135

NPE

Copy your sloccount output file into a separate folder and set your workspace accordingly. For example: The new created folder is: /tmp/jenkins_test And the complete path to the sloccount file is: /tmp/jenkins_test/result.sc Set your workspace to: /tmp/jenkins_test Your test job should have no build actions. Only the sloccount output file shall be processed! Therefore, don't forget to set the search pattern for the sloccount file accordingly. The search pattern should be: result.sc Now, you should have a clean test environment...

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

Karsten Brandt commented on JENKINS-14135

NPE

Hello Carsten, I've an another idea. Has your real jenkins project a long build history? If so, please, create a new jenkins job for tests. So, we can exclude problems caused by older builds from other plugin versions. Regards, Karsten

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

Carsten Otto commented on JENKINS-14135

NPE

I configured a new job that only uses the SLOCcount plugin and has a custom working space that only contains the contents of the ZIP file. This still fails (with 1.8, not with 1.7). It even fails with a directory that just contains the report.sc (and the search pattern is changed to just "report.sc").

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

Carsten Otto commented on JENKINS-14135

NPE

Linux, Debian Stable, x86_64 java version "1.7.0_03" Java(TM) SE Runtime Environment (build 1.7.0_03-b04) Java HotSpot(TM) 64-Bit Server VM (build 22.1-b02, mixed mode) Jenkins ver. 1.472 External Monitor Job Type Plugin 1.0 LDAP Plugin 1.1 pam-auth 1.0 ant 1.1 javadoc 1.0 Jenkins Subversion Plug-in 1.42 Jenkins Translation Assistance plugin 1.9 Jenkins CVS Plug-in 2.4 Jenkins SSH Slaves plugin 0.21 Maven Integration plugin 1.472 Static Analysis Utilities 1.43 Jenkins instant-messaging plugin 1.21 FindBugs Plug-in 4.42 Jenkins Email Extension Plugin 2.22 Jenkins IRC Plugin 2.18 Jenkins Parameterized Trigger plugin 2.15 Jenkins GIT plugin 1.1.20 PMD Plug-in 3.29 Jenkins SLOCCount Plug-in 1.8 Checkstyle Plug-in 3.29 Static Analysis Collector Plug-in 1.29 Jenkins Sonar Plugin 1.8 Join plugin 1.15 Copy Artifact Plugin 1.22 Fail The Build Plugin 1.0 Build Pipeline Plugin 1.3.1 Python Plugin 1.2 Jenkins Workspace Cleanup Plugin 0.8

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

Carsten Otto commented on JENKINS-14135

NPE

Maybe a multithreading problem? I see that you recently introduced a field "report" (that triggers the NPE). Maybe it is necessary to mark this using "volatile"? The effects of the constructor might not yet be visible when invoke() runs.

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

Carsten Otto commented on JENKINS-14135

NPE

I see that this job only works an master and fails on other nodes. Maybe the issue is that "report" is transient, but you do need serialization for the object that is passed to the node? I have no idea how plugins work, but this makes a bit of sense to me.

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

 

Carsten Otto edited a comment on JENKINS-14135

NPE

I see that this job only works on master and fails on other nodes. Maybe the issue is that "report" is transient, but you do need serialization for the object that is passed to the node? I have no idea how plugins work, but this makes a bit of sense to me.

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

Karsten Brandt updated JENKINS-14135

NPE

modified version 1.8 of sloccount plugin
Change By:	Karsten Brandt (30/Jun/12 7:38 AM)
Attachment:	sloccount.hpi

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

Karsten Brandt commented on JENKINS-14135

NPE

I guess you have right. In a remote environment is the serialization of all project data required. And the 'transient' key word prohibits the serialization of report objects. This can lead to the reported problem. Therefore, I have modified the source accordingly. Please try the attached version.

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

 

Karsten Brandt edited a comment on JENKINS-14135

NPE

I guess you have right. In a remote environment is the serialization of all project data required. And the 'transient' key word prohibits the serialization of report objects. This can lead to the reported problem. Therefore, I have modified the source accordingly. Please try the attached version. Make sure, that you start with an empty job history! Older history entries are corrupted.

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

 

Karsten Brandt edited a comment on JENKINS-14135

NPE

I guess you are right. In a remote environment is the serialization of all project data required. And the 'transient' key word prohibits the serialization of report objects. This can lead to the reported problem. Therefore, I have modified the source accordingly. Please try the attached version. Make sure, that you start with an empty job history! Older history entries are corrupted.

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