Commit 77953eb
Publish coverage even when a matrix leg is red
needs.tests.result is the aggregate over the legs, so one failing set took the
whole report down - on exactly the PR whose reader change you wanted to see
covered, since a checksum shift is the usual way a leg goes red. Require only
pytest, and keep needs on the matrix so the artifacts that did upload are
there to combine.
Naming a status function is what disables the implicit success() over all of
needs. A failed leg uploads nothing, so the number is lower on those runs;
the comment says to read it alongside the matrix rather than as a regression.
Checked the degenerate case: with only the pytest data file, combine, xml and
report all succeed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>1 parent 65ad9e1 commit 77953eb
1 file changed
Lines changed: 7 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
97 | 97 | | |
98 | 98 | | |
99 | 99 | | |
100 | | - | |
101 | | - | |
102 | | - | |
103 | | - | |
| 100 | + | |
| 101 | + | |
| 102 | + | |
| 103 | + | |
| 104 | + | |
104 | 105 | | |
105 | | - | |
| 106 | + | |
| 107 | + | |
106 | 108 | | |
107 | 109 | | |
108 | 110 | | |
| |||
0 commit comments