Issue Type: Bug Bug
Assignee: Unassigned
Components: core
Created: 23/May/13 5:47 PM
Description:

Merely calling job.getBuilds().isEmpty() breaks lazy-loading:

at hudson.model.Run.onLoad(Run.java:319)
	at hudson.model.RunMap.retrieve(RunMap.java:226)
	at hudson.model.RunMap.retrieve(RunMap.java:59)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:650)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.all(AbstractLazyLoadRunMap.java:602)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.entrySet(AbstractLazyLoadRunMap.java:264)
	at java.util.AbstractMap$2$1.<init>(AbstractMap.java:378)
	at java.util.AbstractMap$2.iterator(AbstractMap.java:377)
	at hudson.util.RunList$2.iterator(RunList.java:213)
	at hudson.util.RunList.iterator(RunList.java:103)
	at hudson.util.RunList.isEmpty(RunList.java:173)

You would reasonably expect this method, and anything simply iterating builds, to be lazy, but it is eager.

Project: Jenkins
Labels: performance lts-candidate
Priority: Critical Critical
Reporter: Jesse Glick
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/groups/opt_out.
 
 

Reply via email to