Re: CI Testing and failures

From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2020-04-26 16:07:00

On 2020-04-26 18:17, Edward Diener via Boost wrote:
> Sometimes CI testing fails because of a bug in a compiler. It is 
> possible to designate in a jam file that a particular test should not be 
> done for a particular compiler version so that CI testing succeeds, and 
> therefore a PR can be more easily merged because the CI tests "succeed". 
> But then the fact that the compiler has a bug is masked by such a change 
> to the jam file. Is there a solution to such a problem, or maybe this is 
> really not a problem at all ? What do others think about this ?

If the bug affects the library, and you still intend to support it, it 
follows that you have to add a workaround for the bug in the library. 
The failing test indicates that users of this compiler have an actual 
problem.

If you don't intend to support this compile, just remove it from the CI. 
In the old build matrix this can't be done, except to disable it in the 
test/Jamfile.