Recurrent CI failures

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Recurrent CI failures

Nicolas Cellier
Hi all,
for some times we have all the build broken by at least one configuration:

ARCH="linux64x64" FLAVOR="newspeak.cog.spur"

last in date:

This is not sustainable. Most (all ?) of the changes that we are proposing do generate a useless and absolutely unrelated failure status which obstructs the integration of pull requests.

Some time should be invested to solve this problem, arguably by Newspeak teams.
In the interim, I suggest simply declaring this particular flavour as known failure to let a chance to the other jobs finish.