Three tests against the current sentinel-only write_snapshot/load_snapshot: job content round-trip and concurrent-mutation-not-torn genuinely FAIL (RED) since no entity content is written today; write-failure-discard already passes (write_snapshot's open()-failure path already discards correctly) -- flagged transparently as a GREEN-from-day-one regression guard rather than faked RED, per real fault injection (directory removal -> genuine ENOENT). Carries forward two notes for task 2.2: fdatasync's return value is currently unchecked in write_snapshot (persist.c:1505), and a mid-encode- loop fault-injection test should be added once the per-job encode loop exists. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01JDYFbrgyDHbvNYcxApKhrX |
||
|---|---|---|
| .. | ||
| autoscaler | ||
| controller | ||
| docs | ||
| frontend | ||
| include | ||
| lib | ||
| nixSupport | ||
| scheduler | ||
| schema | ||
| tools | ||
| worker | ||
| flake.lock | ||
| flake.nix | ||
| meson.build | ||
| meson.options | ||