-------- Original-Nachricht -------- > Datum: Thu, 31 Jan 2013 19:29:29 -0500 > Von: Jesse Glick <[email protected]> > An: [email protected] > Betreff: Re: Possible fix for JENKINS-15156 (builds disappearing from job > history)
> On 01/31/2013 11:19 AM, Julian Schmidt wrote: > > Below is a patch against revision ce170a60be which for me seems to > > solve this. > > Please submit a pull request—that is the best way to get your changes > reviewed. (If you are reluctant to do that, at least attach the patch to > JIRA.) > > Also, do you know how to reproduce this? A fix this important deserves a > regression test. > I though I did that (see my other reply in this thread), but I never used github before so I might have done it wrong. Creating a regression test for this might be difficult. When my understanding of this bug is correct, then it is triggered by garbage-collection, which does not seem to be 100% deterministic (though I'm no Java expert). I saw this bug sometimes when - creating a new job, triggering builds for it - creating another job - looking at the first job -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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.
