Rongsong Shen
bea956997a
Adds test_handle_jobdispatch_terminal_no_notify_no_leak to test_jobdispatch_no_double_notify.c, closing a gap neither existing test fully covered: test_dispatch_fail_terminal.c (task 3.2) bypasses handle_jobdispatch() entirely via dispatch_a_job_test(), so it can't exercise the double-notify race at all; test_jobdispatch_no_double_notify.c (task 4.1) only proves an aggregate 3-job-batch notify count, not a direct per-job zero-notify proof. The new test drives a single terminal-classified job through the real handle_jobdispatch() entry point and asserts, in one run: JOB_STAT_EXIT with allocs left NULL, a direct (non-aggregate) zero-count read from the notify-capture spy proving no jobDispatchFail was produced for this job, and (via task 3.2's canary-reference technique, armed before the call under test) no reference over-release. Test-only; job.c/handler.c are untouched. RED phase verified via an actual revert-rebuild-rerun of handle_jobdispatch() to its pre-task-4.1 shape. Independently reviewed and approved -- the reviewer notably declined to trust a relayed build report and re-ran verification first-hand before approving. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Cxa1PmqAB5PyXfJaNvj8TN |
||
|---|---|---|
| .. | ||
| settings | ||
| specs | ||
| steering | ||