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

'FATAL: null' while looking for test results in JUnit classes

      Testlink configuration:

      Jenkins configuration:

      Jenkins job FAILS:

      08:23:20  Looking for the test results of TestLink test cases.
      08:23:20  
      08:23:20  Looking for test results in JUnit classes.
      08:23:20  
      08:23:21  FATAL: null
      08:23:21  java.lang.NullPointerException
      08:23:21  	at hudson.plugins.testlink.result.JUnitCaseClassNameResultSeeker.getJUnitNotes(JUnitCaseClassNameResultSeeker.java:138)
      08:23:21  	at hudson.plugins.testlink.result.JUnitCaseClassNameResultSeeker.seek(JUnitCaseClassNameResultSeeker.java:99)
      08:23:21  	at hudson.plugins.testlink.TestLinkBuilder.perform(TestLinkBuilder.java:159)
      08:23:21  	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
      08:23:21  	at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
      08:23:21  	at hudson.model.Build$RunnerImpl.build(Build.java:178)
      08:23:21  	at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
      08:23:21  	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:473)
      08:23:21  	at hudson.model.Run.run(Run.java:1408)
      08:23:21  	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
      08:23:21  	at hudson.model.ResourceController.execute(ResourceController.java:88)
      08:23:21  	at hudson.model.Executor.run(Executor.java:238)
      

      Full console out can be found full-log.txt

      Also JUnit report is attached - TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml

        1. logg.txt
          32 kB
        2. noStrategy.png
          noStrategy.png
          63 kB
        3. withStrategy.png
          withStrategy.png
          77 kB
        4. full-log.txt
          6 kB
        5. jenkins.jpg
          jenkins.jpg
          162 kB
        6. testlink.jpg
          testlink.jpg
          202 kB
        7. TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml
          6 kB

          [JENKINS-13150] 'FATAL: null' while looking for test results in JUnit classes

          Jaroslavas D. created issue -
          Bruno P. Kinoshita made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

          Wow Jaroslavas, nice catch and great report. You provided all the necessary information, thank you very much.

          I will release a new version this week or next week with an enhancement on result notes and bug fixes, including this one.

          Thanks again.
          Bruno

          Bruno P. Kinoshita added a comment - Wow Jaroslavas, nice catch and great report. You provided all the necessary information, thank you very much. I will release a new version this week or next week with an enhancement on result notes and bug fixes, including this one. Thanks again. Bruno

          Jaroslavas, could you tell me which version of the plug-in are you using, please?

          Bruno P. Kinoshita added a comment - Jaroslavas, could you tell me which version of the plug-in are you using, please?

          Jaroslavas D. added a comment - - edited

          It is the last plugin version 3.1.1

          Also, jenkins version is 1.452

          P.S.
          Moreover, I have just updated my local jenkins to the last version (1.456). And seems what TestLink plugin doesn't work at all.. I don't really understand if it is my local jenkins' problem or plugin'. But when I try to add build step named 'Invoke TestLink' - nothing happens.. I mean, in job configuration when I click 'Invoke TestLink' I expect new fields for plugin configuration.. but literary - nothing happens. Please, check plugin compatibility with the newest jenkins' version.

          Thank you!

          Jaroslavas D. added a comment - - edited It is the last plugin version 3.1.1 Also, jenkins version is 1.452 P.S. Moreover, I have just updated my local jenkins to the last version (1.456). And seems what TestLink plugin doesn't work at all.. I don't really understand if it is my local jenkins' problem or plugin'. But when I try to add build step named ' Invoke TestLink ' - nothing happens.. I mean, in job configuration when I click ' Invoke TestLink ' I expect new fields for plugin configuration.. but literary - nothing happens. Please, check plugin compatibility with the newest jenkins' version. Thank you!

          That's very strange, I've noticed it in 1.455 too, but I can't tell yet what is happening. There is no change that would cause such issue in 1.455, so I'm assuming it might be something related to the new changes in Jenkins UI. I'll investigate to find out what is causing this issue and how I could fix it in the plug-in.

          Thanks

          Bruno P. Kinoshita added a comment - That's very strange, I've noticed it in 1.455 too, but I can't tell yet what is happening. There is no change that would cause such issue in 1.455, so I'm assuming it might be something related to the new changes in Jenkins UI. I'll investigate to find out what is causing this issue and how I could fix it in the plug-in. Thanks

          Jaroslavas D. added a comment -

          Bruno,

          I am not sure about exact version.. is it any way to figure out testlink plugin version without administrator rights? I don't have direct permission to manage plugins..

          Jaroslavas D. added a comment - Bruno, I am not sure about exact version.. is it any way to figure out testlink plugin version without administrator rights? I don't have direct permission to manage plugins..

          Removed junit and plugins components

          Bruno P. Kinoshita added a comment - Removed junit and plugins components
          Bruno P. Kinoshita made changes -
          Component/s Original: plugin [ 15491 ]
          Component/s Original: junit [ 15499 ]

          The only way that I know is by having a look at the plug-ins configuration screen. Maybe someone with admin access could tell which version you're using? I know there was a fixed NullPointerException in the same part of the code, but it was fixed in 3.1.1. If you could have a look on it, that would help a lot

          I had a look at the code here, and everything seems fine. The changes that I mentioned are related to include more details, like which method passed and which failed, in the test execution notes.

          Sorry for not being able to help you finding the plug-in version. We could add the plug-in version in the console too in future versions, but that could cause problems if someone (specially dumb me forgot to update the text displayed in the console.

          Bruno

          Bruno P. Kinoshita added a comment - The only way that I know is by having a look at the plug-ins configuration screen. Maybe someone with admin access could tell which version you're using? I know there was a fixed NullPointerException in the same part of the code, but it was fixed in 3.1.1. If you could have a look on it, that would help a lot I had a look at the code here, and everything seems fine. The changes that I mentioned are related to include more details, like which method passed and which failed, in the test execution notes. Sorry for not being able to help you finding the plug-in version. We could add the plug-in version in the console too in future versions, but that could cause problems if someone (specially dumb me forgot to update the text displayed in the console. Bruno

            kinow Bruno P. Kinoshita
            jar Jaroslavas D.
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: