Get rid of red crosses in the CI reports #267
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should be the first PR in a long time without the annoying red crosses in the CI report.
Several jobs in our CI workflows are known to fail. Currently, we set
continue-on-error: true
for them. This makes at least the workflow status green. However, the red crosses pop up in the PR and commit CI reports. Getting used to them does not look like a good idea to me. One way of dealing with it is to simply remove the jobs. That would be fine with me but I accept the arguments for keeping them.Job
cce-gpu-openmp
is known to fail at the runtime. This PR changes it so that it is marked green if it does fail at the runtime and is considered as failed otherwise. That is, the job fails the wholeSelf-hosted CI
workflow if it does NOT fail against the expectations.The
ifx
+accel
jobs are known to fail at the build time due to internal compiler errors. This PR changes them so that they are marked green if they fail at the build time with theInternal compiler error
substring in the build log. In all other cases, the jobs fail the wholeContinuous integration in a box
.