On Jan 26, 2018, at 09:13, Marcus Denker <marcus.denker@inria.fr> wrote:
Hello,
Yes⦠I try to make notes about all failing test so we can detect patterns
Will you share the notes?
It seems most of them are related to timing issues that come from the fact that it runs on a virtualised box⦠Others are related to the fact that we run multiple instances in parallel on the same machine and they try to open the same port. (not that often).
That part can be fixed using port 0 in corresponding test cases. It opens a free port. Cheers, Juraj
Another problem is that the vm sometimes crashes (related to the font rendering bug)
We really need to try to find a way to stabilise the CI.
Marcus
On 26 Jan 2018, at 10:23, Torsten Bergmann <astares@gmx.de> wrote:
While our general build from Pharo 7 is (more or less often) green
https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%20...
I've noticed more and more that the CI builds for the PR's to Pharo 7 even for trivial changes are often broken and not green
https://github.com/pharo-project/pharo/pulls
which is annoying and one still has the feeling to break the builds.
As always I think getting a more stable CI is dependent on time, resources and priorities. But does anyone know if this is a general issue or something that is already worked on?
Thx T.