Details
-
Bug
-
Status: Open (View Workflow)
-
Critical
-
Resolution: Unresolved
-
centos 6
Description
Using TAP plugin v1.9 and Jenkins v1.496, the attached stack trace occurs in a loop when Jenkins is restarted. We are now seeing this prevent Jenkins starting up.
Our Service Engineer tells me that the plugin is unable to load the attached build.xml
Apart from becoming larger in size, the TAP test results we are producing have not changed appreciably to cause this problem.
Attachments
Activity
Alex, could you confirm if the build.xml attached, is the one that is failing, please? I couldn't reproduce the error using your build.xml in my tests (link above).
Cheers, B
Hi Alex, I'm starting a cycle to work on other Open Source projects. Feel free to update this issue. My next Jenkins Plug-ins cycle will happen within few weeks.
Cheers, Bruno
Alex Newnham
added a comment - New stack trace as requested.
One way to trigger the problem is to kill the subprocess triggered by Jenkins that will ultimately produce the TAP.
Alex Newnham
added a comment - New stack trace as requested.
One way to trigger the problem is to kill the subprocess triggered by Jenkins that will ultimately produce the TAP. Ok, I have a new cycle to work on TAP plug-in. Time to give it another try :o)
Created a sample repository [1] at GitHub to isolate the issue.
There I used the same xstream library as Jenkins 1.496, as well as same tap4j as TAP Plug-in 1.9 (3.3).
Unfortunately (or fortunately) I didn't see the same error. Maybe I'm missing something, so I'll continue to investigate.
[1] https://github.com/tupilabs/xstream-sandbox