Commit 25847dd
committed
CI: Ensure code coverage is always uploaded
If code coverage is not uploaded on failure, then overall coverage can
suffer mysteriously (e.g., if a mac system failed, then it would appear
as if `backend_macosx.py` was not tested). Codecov would then show
several "indirect changes" that are spurious.
On GitHub Actions, if you don't have any status check function in the
`if` entry, then it is treated as `success() && (whatever else you
had)`, so put in an explicit check.
Azure also had no condition, so defaulted to only-on-success.
Cygwin is only run on `main` and sometimes on PRs, so disable code
coverage reporting from it. That would cause random "reductions" in
coverage for all PRs that don't run it (which is most of them.)
Also, fix the image-cleanup script, which would only run on success
instead of failure, where it would be useful.1 parent ce15014 commit 25847dd
3 files changed
+6
-7
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
245 | 245 | | |
246 | 246 | | |
247 | 247 | | |
248 | | - | |
249 | | - | |
250 | | - | |
251 | | - | |
252 | | - | |
253 | | - | |
| 248 | + | |
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
316 | 316 | | |
317 | 317 | | |
318 | 318 | | |
| 319 | + | |
319 | 320 | | |
320 | 321 | | |
321 | 322 | | |
| |||
349 | 350 | | |
350 | 351 | | |
351 | 352 | | |
| 353 | + | |
352 | 354 | | |
353 | 355 | | |
354 | 356 | | |
| |||
364 | 366 | | |
365 | 367 | | |
366 | 368 | | |
367 | | - | |
| 369 | + | |
368 | 370 | | |
369 | 371 | | |
370 | 372 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
268 | 268 | | |
269 | 269 | | |
270 | 270 | | |
| 271 | + | |
271 | 272 | | |
272 | 273 | | |
273 | 274 | | |
274 | 275 | | |
275 | 276 | | |
| 277 | + | |
276 | 278 | | |
277 | 279 | | |
278 | 280 | | |
| |||
0 commit comments