Re: [Pharo-dev] [ Pharo 70 ] Build 52 to 54

2017-09-04 Thread Guillermo Polito
On Thu, Aug 24, 2017 at 2:16 PM, Ben Coman wrote: > > > On Tue, Aug 22, 2017 at 11:51 PM, Guillermo Polito < > guillermopol...@gmail.com> wrote: > >> Hi Marcus, >> >> Please, do not relaunch the build if there is a test failure. That >> simply does not fix the problem, it just adds noise. There a

Re: [Pharo-dev] [ Pharo 70 ] Build 52 to 54

2017-08-24 Thread Ben Coman
On Tue, Aug 22, 2017 at 11:51 PM, Guillermo Polito < guillermopol...@gmail.com> wrote: > Hi Marcus, > > Please, do not relaunch the build if there is a test failure. That > simply does not fix the problem, it just adds noise. There are two > problems: > > 1) we have some sporadic test failures (so

Re: [Pharo-dev] [ Pharo 70 ] Build 52 to 54

2017-08-22 Thread Stephane Ducasse
I started the list of fleaky tests at the end of this document https://docs.google.com/document/d/13Zv-za9V54aurmRwHSgObqGecN9PY8rc-t8U_oI_s-w/edit On Tue, Aug 22, 2017 at 7:12 PM, Stephane Ducasse wrote: > Hi denis > > you can have a look at > https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pe

Re: [Pharo-dev] [ Pharo 70 ] Build 52 to 54

2017-08-22 Thread Stephane Ducasse
Hi denis you can have a look at https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20and%20branch%20Pipeline/job/development/ I started to crawl this list and log the sporadic failing tests. But I do it when integrating. Stef On Tue, Aug 22, 2017 at 6:41 PM, Denis Kudrias

Re: [Pharo-dev] [ Pharo 70 ] Build 52 to 54

2017-08-22 Thread Stephane Ducasse
On Tue, Aug 22, 2017 at 5:51 PM, Guillermo Polito wrote: > Hi Marcus, > > Please, do not relaunch the build if there is a test failure. That > simply does not fix the problem, it just adds noise. There are two > problems: > > 1) we have some sporadic test failures (sometimes network, sometimes > s

Re: [Pharo-dev] [ Pharo 70 ] Build 52 to 54

2017-08-22 Thread Denis Kudriashov
Hi. > 1) we have some sporadic test failures (sometimes network, sometimes > some mutex or delay issues). They do not happen all the time and > that's why sometimes there is one or two failing tests. We should > detect these tests and fix them to be more robust I thing I am responsible for Mute

Re: [Pharo-dev] [ Pharo 70 ] Build 52 to 54

2017-08-22 Thread Guillermo Polito
Hi Marcus, Please, do not relaunch the build if there is a test failure. That simply does not fix the problem, it just adds noise. There are two problems: 1) we have some sporadic test failures (sometimes network, sometimes some mutex or delay issues). They do not happen all the time and that's w

[Pharo-dev] [ Pharo 70 ] Build 52 to 54

2017-08-22 Thread Marcus Denker
[ Pharo 70 ] Build 52 PR 205 index-inst-var-should-move-from-Slot-to-IndexedSlot https://github.com/pharo-project/pharo/pull/205 https://pharo.fogbugz.com/f/cases/20191 Build 53: failed, redone as 54 [ Pharo 70 ] Build 54 PR 193 Integrate WebBrowser-Core package to be able to op