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

Unable to see "Test Result Trends"

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      After upgrading the Junit plugin i am getting the following issue:

      • If a job is only having only one build then it shows the "Test Result trends".
      • If number of builds for a job is greater than 1, then it just shows the loading animation.
      • This was working before the Junit plugin update.

      I have seen all the issues opened regarding this but none solves my query.

      Is this a bug in Junit plugin or Jenkins core itself?

       

       

       

      Jenkins version : 2.249.2
      Junit plugin : 1.43

        Attachments

          Activity

          Hide
          timja Tim Jacomb added a comment - - edited

          is there anything in the server logs?

          what type of jobs?

          steps to reproduce?

          Show
          timja Tim Jacomb added a comment - - edited is there anything in the server logs? what type of jobs? steps to reproduce?
          Hide
          hellspam Roy Arnon added a comment -

          We also had the same issue.

          I am not sure we both have the exact same issue, but I noticed in the logs that we have this message:

          WARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving https://jenkins/$stapler/bound/c8a1f0cb-0ff6-45ac-aaa0-907ed474e917/getBuildTrendModelWARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving https://jenkins/$stapler/bound/c8a1f0cb-0ff6-45ac-aaa0-907ed474e917/getBuildTrendModeljava.lang.IllegalStateException: Label already registered: 20201110.23-RELEASE at edu.hm.hafner.echarts.LinesDataSet.add(LinesDataSet.java:67) at edu.hm.hafner.echarts.LinesDataSet.add(LinesDataSet.java:90) at edu.hm.hafner.echarts.SeriesBuilder.createDataSetPerBuildNumber(SeriesBuilder.java:148) at edu.hm.hafner.echarts.SeriesBuilder.createDataSet(SeriesBuilder.java:82) at hudson.tasks.test.TestResultTrendChart.create(TestResultTrendChart.java:27) at hudson.tasks.test.TestResultProjectAction.createChartModel(TestResultProjectAction.java:122) at hudson.tasks.test.TestResultProjectAction.getBuildTrendModel(TestResultProjectAction.java:203) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)
          

           

          We do use the same labels (build name) for our builds sometimes, especially in cases that some stage failed. I deleted the offending duplicate build, and the Test results then appeared fine.

          Is it possible to support duplicate labels for builds? 

          Show
          hellspam Roy Arnon added a comment - We also had the same issue. I am not sure we both have the exact same issue, but I noticed in the logs that we have this message: WARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving https: //jenkins/$stapler/bound/c8a1f0cb-0ff6-45ac-aaa0-907ed474e917/getBuildTrendModelWARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving https://jenkins/$stapler/bound/c8a1f0cb-0ff6-45ac-aaa0-907ed474e917/getBuildTrendModeljava.lang.IllegalStateException: Label already registered: 20201110.23-RELEASE at edu.hm.hafner.echarts.LinesDataSet.add(LinesDataSet.java:67) at edu.hm.hafner.echarts.LinesDataSet.add(LinesDataSet.java:90) at edu.hm.hafner.echarts.SeriesBuilder.createDataSetPerBuildNumber(SeriesBuilder.java:148) at edu.hm.hafner.echarts.SeriesBuilder.createDataSet(SeriesBuilder.java:82) at hudson.tasks.test.TestResultTrendChart.create(TestResultTrendChart.java:27) at hudson.tasks.test.TestResultProjectAction.createChartModel(TestResultProjectAction.java:122) at hudson.tasks.test.TestResultProjectAction.getBuildTrendModel(TestResultProjectAction.java:203) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)   We do use the same labels (build name) for our builds sometimes, especially in cases that some stage failed. I deleted the offending duplicate build, and the Test results then appeared fine. Is it possible to support duplicate labels for builds? 
          Hide
          timja Tim Jacomb added a comment - - edited

          There’s another issue for that somewhere, Ulli Hafner fyi

          https://issues.jenkins.io/browse/JENKINS-63338

          Show
          timja Tim Jacomb added a comment - - edited There’s another issue for that somewhere, Ulli Hafner fyi https://issues.jenkins.io/browse/JENKINS-63338
          Hide
          daniel_jeznach_img Daniel Jeznach added a comment -

          The same here, if pipeline job has duplicating build names, the bug occurs. After I have manually deleted all repeating builds, test results trends display correctly.

          Show
          daniel_jeznach_img Daniel Jeznach added a comment - The same here, if pipeline job has duplicating build names, the bug occurs. After I have manually deleted all repeating builds, test results trends display correctly.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            kartikeyachauhan Kartikeya Chauhan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: