Commit 88276fa
test: say why the pipeline abandoned, instead of only that it did
This test failed on a Linux runner and passed everywhere else, and the log carried
`assert 'abandoned' == 'verified'` and nothing more. No production code had changed
since the last run whose suite was green, so the cause is environmental -- but the run
executes a compiler and a package download, and the failure message cannot tell a
broken toolchain from a broken patch.
The state already holds the answer. `abandon_reason`, `verify_ok`, `prepare_ok`,
`static_fatal` and the rest are each set by the node that decided, so rendering them
into the assertion costs nothing on a pass and turns the next failure into a
diagnosis. Verified by flipping the expected value and reading what printed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>1 parent 4d2a4c3 commit 88276fa
1 file changed
Lines changed: 19 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
238 | 238 | | |
239 | 239 | | |
240 | 240 | | |
| 241 | + | |
| 242 | + | |
| 243 | + | |
| 244 | + | |
| 245 | + | |
| 246 | + | |
| 247 | + | |
| 248 | + | |
| 249 | + | |
| 250 | + | |
| 251 | + | |
| 252 | + | |
| 253 | + | |
| 254 | + | |
| 255 | + | |
| 256 | + | |
| 257 | + | |
241 | 258 | | |
242 | 259 | | |
243 | 260 | | |
| |||
271 | 288 | | |
272 | 289 | | |
273 | 290 | | |
274 | | - | |
275 | | - | |
| 291 | + | |
| 292 | + | |
276 | 293 | | |
277 | 294 | | |
278 | 295 | | |
| |||
0 commit comments