-
Bug
-
Resolution: Fixed
-
Critical
Setup is the same as in JENKINS-23945 except use the testng branch of the sample project, and configure the TestNG plugin's publisher with **/target/surefire-reports/testng-results.xml. Even with the fix of JENKINS-23945 applied to Jenkins core, after displaying the job index page all builds are loaded:
... FINER hudson.model.Run reload lazy-load-perf #71 @... ... FINEST hudson.model.RunMap Loaded lazy-load-perf #71 hudson.model.RunMap$ThisIsHowItsLoaded at hudson.model.RunMap.retrieve(RunMap.java:221) at hudson.model.RunMap.retrieve(RunMap.java:56) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:688) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:650) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:382) at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:70) at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:59) at java.util.AbstractMap$2$1.next(AbstractMap.java:385) at hudson.util.RunList.size(RunList.java:108) at hudson.plugins.testng.TestNGProjectAction.newGraphNotNeeded(TestNGProjectAction.java:141) at hudson.plugins.testng.TestNGProjectAction.doGraph(TestNGProjectAction.java:114) at ...
The problem is TestNGProjectAction.newGraphNotNeeded calling RunList.size, which is deprecated since it forces all builds to be loaded immediately.
- is blocking
-
JENKINS-23945 Test result trend breaks lazy-loading
- Resolved
-
JENKINS-9839 Trend graph is not correctly updated if builds are deleted
- Closed