The issue shouldn't happen again now. Previously I had two executor threads running on Jenkins, so this allowed more than one build at one time. There's really no need for that, so I reduced it to one executor so that this prevents any interference from simultaneous commits.
GC On Wed, Aug 8, 2012 at 9:39 AM, Gregory Casamento <[email protected]> wrote: > I believe what happened here is that we had two commits very close > together. So both were fired off at the same time and interfered > with one another and caused a false alarm. > > I will figure out how to correct this. :) > > GC > > On Wed, Aug 8, 2012 at 8:13 AM, Riccardo Mottola > <[email protected]> wrote: >> Hi, >> >> [email protected] wrote: >>> >>> See <http://gnustep.dnsalias.org:8080/job/gnustep/245/changes> >>> >>> >> I think something was bogus here? :) >> >> Riccardo > > > > -- > Gregory Casamento > Open Logic Corporation, Principal Consultant > yahoo/skype: greg_casamento, aol: gjcasa > (240)274-9630 (Cell) > http://www.gnustep.org > http://heronsperch.blogspot.com -- Gregory Casamento Open Logic Corporation, Principal Consultant yahoo/skype: greg_casamento, aol: gjcasa (240)274-9630 (Cell) http://www.gnustep.org http://heronsperch.blogspot.com _______________________________________________ Gnustep-dev mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnustep-dev
