Branch: refs/heads/master
Home: https://github.com/jenkinsci/jenkins
Commit: 972d8bad229a4be6d98c8fcaad6880e1351af3ee
https://github.com/jenkinsci/jenkins/commit/972d8bad229a4be6d98c8fcaad6880e1351af3ee
Author: Jesse Glick <[email protected]>
Date: 2013-05-28 (Tue, 28 May 2013)
Changed paths:
M changelog.html
M core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java
M core/src/test/java/jenkins/model/lazy/AbstractLazyLoadRunMapTest.java
Log Message:
-----------
[FIXED JENKINS-15652] “Solving” errors by just return null from ALLRM.search
and reducing to one-line warnings.
@kohsuke confirms that the intent of throwing AIOOBE was to track down definite
code errors;
but in at least some known occurrences of this bug, the problem is invalid data:
build records on disk with <number>s that are duplicated and/or out of order.
Since that violates the precondition of the class, we do not pretend to
successfully search for such records.
At some point it would make sense to have the code detect anomalous conditions
and initiate a builds folder cleanup.
Take only the last build of a given number, and discard any earlier with higher
number.
I.e. just set <number> to 0 or something and ignore such builds, or rename
build.xml to build-broken.xml.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Commits" 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.
