Commit 8226543
\
CI on Linux runs both per-stage commits to completion (separate \`git
commit\` calls for each .dvc, no \`.git/index.lock\` race); my local
macOS run consistently sees one of the two get dropped. Both are
valid pre-existing behavior for \`--push end\` (end-of-run cache push
uses \`executed\` results, not commits). Assert the committed-subjects
set is in \`{ {"Run a"}, {"Run b"}, {"Run a", "Run b"} }\`.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>test_push_end_batches_cache_pushes\: accept both race outcomes1 parent 7415af6 commit 8226543
1 file changed
Lines changed: 12 additions & 11 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
272 | 272 | | |
273 | 273 | | |
274 | 274 | | |
275 | | - | |
276 | | - | |
277 | | - | |
| 275 | + | |
| 276 | + | |
| 277 | + | |
| 278 | + | |
| 279 | + | |
278 | 280 | | |
279 | | - | |
280 | | - | |
281 | | - | |
282 | | - | |
283 | | - | |
284 | | - | |
285 | | - | |
286 | | - | |
| 281 | + | |
| 282 | + | |
| 283 | + | |
| 284 | + | |
| 285 | + | |
| 286 | + | |
| 287 | + | |
287 | 288 | | |
288 | 289 | | |
289 | 290 | | |
| |||
0 commit comments