[Pharo-dev] CI Hickups ...

Stephane Ducasse stepharo.self at gmail.com
Sun Jan 28 16:43:22 EST 2018


thanks marcus.
I was wondering if we should not buy a fast machine just for the slaves.
It would be good invested money because we lose too much time for that.

stef

On Sun, Jan 28, 2018 at 8:06 PM, Marcus Denker <marcus.denker at inria.fr> wrote:
>
>
>> On 26 Jan 2018, at 15:06, Marcus Denker <marcus.denker at inria.fr> wrote:
>>
>>
>>
>>> On 26 Jan 2018, at 14:42, Juraj Kubelka <juraj.kubelka at icloud.com> wrote:
>>>
>>>
>>>
>>>> On Jan 26, 2018, at 09:13, Marcus Denker <marcus.denker at inria.fr> wrote:
>>>>
>>>> Hello,
>>>>
>>>> Yes… I try to make notes about all failing test so we can detect patterns
>>>>
>>>
>>> Will you share the notes?
>>>
>>
>> Here are some from todays reviews:
>>
>> testPatch – MacOS32.Zinc.Tests.ZnClientTests
>>       Failed to start server on port 1719. Is there one already?
>>
>>
>> testTwiceDeliveredDataSholdBeDetected – MacOS32.GT.EventRecorder.Tests.Core.GTEventRecorderTest
>> testTwiceDeliveredDataSholdBeDetected – Windows32.GT.EventRecorder.Tests.Core.GTEventRecorderTest
>> testDeliverNow3 – Windows32.GT.EventRecorder.Tests.Core.GTEventRecorderTest
>> testDeliverNow2 – Windows32.GT.EventRecorder.Tests.Core.GTEventRecorderTest
>> testAddCollector3 – Windows32.GT.EventRecorder.Tests.Core.GTEventRecorderTest
>> testNotDeliveredDataShouldBeResent – Windows32.GT.EventRecorder.Tests.Core.GTEventRecorderTest
>>
>>
>> testGetPharoVersion – MacOS32.Zinc.Zodiac.ZnHTTPSTests
>>
>> testExecuteOnceAfterSchedulingMultipleTimes – MacOS32.OmbuTests.OmDeferrerTest
>>
>
> More interesting data points:
>
> -> end of the week (Friday to Sunday) most of the fails happened due to the macOS Slave being not
>     in a good state. I killed the virtual server and re-created it sunday evening
> -.> after that, we got quite a lot of successful green CI runs. As this is Sunday, my guess
> is that the load on the CI infrastructure is fairly low.
>
> ==> what we need to do:
> 1) dead infrastructure cases need to be detected somehow.
> 2) the CI infrastructure overload seems to be the root of the problem to some extend.
>
>         Marcus
>
>




More information about the Pharo-dev mailing list