Extends task 2.1's test_scheduler_dispatch_commit.c with two tests proving resource-in-use accounting survives more than a single round boundary between dispatch and worker confirmation, per task 5.1's "several rounds" / "matching a same-round confirmation" language: - test_dispatch_commit_survives_several_rounds_before_confirmation: loops 5 round-boundary cycles, asserting resInUse after EVERY round, not just once. - test_dispatch_commit_multi_round_gap_matches_same_round_confirmation: compares resInUse after 1 round vs after 5 rounds and asserts equality -- a same-round confirmation is modeled as nrounds==1 since design.md documents re-applying JOB_STAT_RUN to an already-RUN job as a confirmed no-op, so resInUse depends only on job->state, never on confirmation timing. Test-only; scheduler.c is untouched. RED phase independently verified by both implementer and reviewer via an actual revert-rebuild-rerun cycle (4/5 tests fail without the task 2.1 fix). Independently reviewed and approved. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Cxa1PmqAB5PyXfJaNvj8TN |
||
|---|---|---|
| .. | ||
| settings | ||
| specs | ||
| steering | ||