Jesse Glick commented on Bug JENKINS-24176

Experimenting with reverting the fix of JENKINS-9839. While that issue might be an annoyance in unusual cases, it is minor compared to the lazy-loading problem, which can bring a large Jenkins installation to a grinding halt—just because someone opened a job index page in a browser. Now the next problem appears:

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.LazyBuildMixIn$RunMixIn.getPreviousBuild(LazyBuildMixIn.java:366)
	at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:198)
	at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:106)
	at hudson.model.Run.getPreviousCompletedBuild(Run.java:819)
	at hudson.plugins.testng.TestNGProjectAction.populateDataSetBuilder(TestNGProjectAction.java:187)
	at hudson.plugins.testng.TestNGProjectAction.doGraph(TestNGProjectAction.java:112)
	at …
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to