It looks to me like the additional builds in the list are due to maven submodule builds where the top level build record no longer exists. I added debug into the removal codepath where it detects a null r value and the ones it is removing correspond to build records that only exist at the lower level

11-Oct-2012 01:21:42 jenkins.model.lazy.AbstractLazyLoadRunMap search
WARNING: r was null for pivot=0, id=2010-10-28_01-01-34

richm@royalcounty:~$ find /opt/hudson/jobs/tcserv -name 2010-10-28_01-01-34
/opt/hudson/jobs/tcserv/modules/a.b.c$m1/builds/2010-10-28_01-01-34
/opt/hudson/jobs/tcserv/modules/a.b.c$m2/builds/2010-10-28_01-01-34
/opt/hudson/jobs/tcserv/modules/a.b.c$m3/builds/2010-10-28_01-01-34
/opt/hudson/jobs/tcserv/modules/a.b.c$m4/builds/2010-10-28_01-01-34
/opt/hudson/jobs/tcserv/modules/a.b.c$m5/builds/2010-10-28_01-01-34
/opt/hudson/jobs/tcserv/modules/a.b.c$m6/builds/2010-10-28_01-01-34
/opt/hudson/jobs/tcserv/modules/a.b.c$m7/builds/2010-10-28_01-01-34
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

Reply via email to