The basic idea is not to fail a CI check if the PR branch is not the cause.

Currently, 

(1) "Build & Test / test-long" sometimes fails. 
(2) It occurs frequently that one of "Build & Test using Conda(Meson) / 
Conda" checks fails. 

(1) is unfortunate, but this is our main engine checking the PR branch. We 
should live with it, hoping someone to fix it.

For (2), I suggest to make the checks information only; the check report 
failed step, but the check itself passes always. 

It seems that this can be implemented by adding

- name: Force job success 
  if: always() 
  run: exit 0 # Ensure job always passes

as the last step of the job for the check.



-- 
You received this message because you are subscribed to the Google Groups 
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-devel+unsubscr...@googlegroups.com.
To view this discussion visit 
https://groups.google.com/d/msgid/sage-devel/b52e08a7-41f0-40a2-bad1-8fd26ed17c52n%40googlegroups.com.

Reply via email to