[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Jenkins build is back to normal : gnustep #245
From: |
Gregory Casamento |
Subject: |
Re: Jenkins build is back to normal : gnustep #245 |
Date: |
Wed, 8 Aug 2012 10:36:14 -0400 |
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
<address@hidden> 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
> <address@hidden> wrote:
>> Hi,
>>
>> address@hidden 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