Uh oh!
There was an error while loading. Please reload this page.
Treat warnings as errors in CI - #924
Conversation
This helps avoid accidentally missing a warning.
e7ca6d6 to
d682500Comparebluss
commented
Feb 18, 2021
I'm thinking we maybe want to have the continue on error flag set on the clippy job (so that other tests also run) (?) |
d682500 to
2ea7503Compare| vec![ | ||
| arr2(&[[7.], [6.], [5.]]), | ||
| arr2(&[[4.], [3.], [2.]]), | ||
| arr2(&[[1.], [0.]]), |
There was a problem hiding this comment.
Unused import of arr2 when the std feature is not enabled. There were a number of other similar unused import warnings.
2ea7503 to
a5d2ff4Comparejturner314
commented
Feb 18, 2021
I think they were running. (I was just force-pushing to fix warnings before they got a chance to finish.) I have seen items canceled when other items fail, but from what I've seen, it's always been within a job (i.e. within "tests" or within "cross_test"), so the tests should still run if clippy fails. I'll check to make sure. |
bluss
commented
Feb 18, 2021
I think you'd want continue on error, but yeah I wonder why they are running anyway. https://github.com/petgraph/petgraph/blob/master/.github/workflows/ci.yml#L45 |
I came across these pages regarding continue-on-error:
which seem to indicate that continue-on-error makes the job always "pass", i.e. get a green check. They suggest to use I'll try adding Edit: Yes, the canceling of items appears to occur within jobs, but not across jobs. (The jobs are |
0049144 to
8e75d9dCompare8e75d9d to
87a6448Comparebluss
commented
Mar 4, 2021
Thanks |
This helps avoid accidentally missing a warning.