Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-17215

TAP plugin can prevent Jenkins startup

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Component/s: tap-plugin
    • Labels:
    • Environment:
      centos 6
    • Similar Issues:

      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

        1. build.xml
          65 kB
        2. stack2.txt
          16 kB
        3. stack3.txt
          15 kB
        4. stack4.txt
          13 kB

          Activity

          Hide
          kinow Bruno P. Kinoshita added a comment -

          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

          Show
          kinow Bruno P. Kinoshita added a comment - 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
          Hide
          kinow Bruno P. Kinoshita added a comment -

          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

          Show
          kinow Bruno P. Kinoshita added a comment - 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
          Hide
          kinow Bruno P. Kinoshita added a comment -

          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

          Show
          kinow Bruno P. Kinoshita added a comment - 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
          Hide
          alex_n 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.

          Show
          alex_n 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.
          Hide
          kinow Bruno P. Kinoshita added a comment -

          Ok, I have a new cycle to work on TAP plug-in. Time to give it another try :o)

          Show
          kinow Bruno P. Kinoshita added a comment - Ok, I have a new cycle to work on TAP plug-in. Time to give it another try :o)

            People

            • Assignee:
              kinow Bruno P. Kinoshita
              Reporter:
              alex_n Alex Newnham
            • Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated: