[Pharo-dev] Pharo Process question

Stephane Ducasse stepharo.self at gmail.com
Wed Oct 25 12:51:44 EDT 2017


Well I would dream to give my superpower to attract bugs to anybody else.
Because sometimes this is tiring.
Yesterday a class comment changes of mine broke our jenkins process. Do not
ask me why and how it is possible.
But it did.

Stef

On Wed, Oct 25, 2017 at 12:40 PM, Norbert Hartl <norbert at hartl.name> wrote:

> But don't complain for the coming weeks about things not working ;)
>
> Norbert
>
> Am 25.10.2017 um 12:16 schrieb Stephane Ducasse <stepharo.self at gmail.com>:
>
> Thanks guys.
> Let us move to tonel :)
> So I have to watch out then before pushing the button ;)
> Stef
>
>
> On Wed, Oct 25, 2017 at 10:10 AM, Guillermo Polito <
> guillermopolito at gmail.com> wrote:
>
>>
>>
>> On Tue, Oct 24, 2017 at 9:49 PM, Esteban Lorenzano <estebanlm at gmail.com>
>> wrote:
>>
>>>
>>>
>>> > On 24 Oct 2017, at 21:47, Stephane Ducasse <stepharo.self at gmail.com>
>>> wrote:
>>> >
>>> > Hi
>>> >
>>> > are the pending PR reevaluated when one PR is integrated?
>>>
>>
>> Unfortunately not on every integration... We should do it that way but
>> there are some problems with Jenkins allocating space in the master machine.
>>
>> Christophe was telling me he would contact the people from jenkins to see
>> if there is a solution for that.
>>
>>>
>>> it was, but Guille disabled it because it was killing the server.
>>> when we jump to tonel we can re-evaluate the problem :)
>>>
>>> Esteban
>>>
>>> >
>>> > Stef
>>> >
>>>
>>>
>>>
>>
>>
>> --
>>
>> Guille Polito
>> Research Engineer
>>
>>
>> Centre de Recherche en Informatique, Signal et Automatique de Lille
>> CRIStAL - UMR 9189
>> French National Center for Scientific Research - *http://www.cnrs.fr
>> <http://www.cnrs.fr/>*
>>
>> *Web:* *http://guillep.github.io* <http://guillep.github.io/>
>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013>
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20171025/90306490/attachment-0002.html>


More information about the Pharo-dev mailing list