Skip to content
  1. May 31, 2013
  2. May 29, 2013
    • Jesse Glick's avatar
      [FIXED JENKINS-15652] “Solving” errors by just return null from ALLRM.search... · 972d8bad
      Jesse Glick authored
      [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.
      972d8bad
    • Jesse Glick's avatar
      fff90c10
  3. May 28, 2013
  4. May 24, 2013
  5. May 23, 2013
  6. May 21, 2013
  7. May 20, 2013
  8. May 19, 2013
  9. May 17, 2013
  10. May 16, 2013
  11. May 15, 2013
  12. May 13, 2013
  13. May 10, 2013
  14. May 08, 2013
  15. May 07, 2013
  16. May 06, 2013
  17. May 02, 2013
  18. May 01, 2013
  19. Apr 30, 2013
  20. Apr 29, 2013
Loading