Rongsong Shen
8607348c9b
sched_commit_decision()'s DISPATCH branch now sets job->state = JOB_STAT_RUN in the same operation that already commits job->allocs/job->accounts, per Requirement 1.1/1.2/1.3. sched_account_jobs()'s existing JOB_IS_RUN gate is unmodified -- this closes bug-1624 by giving it the input it was missing: a dispatched job now survives a round boundary in resource-in-use totals regardless of how many rounds pass before worker confirmation arrives. Regression test drives the real, unmodified sched_account_jobs() across a simulated round boundary (resInUse reset, no confirmation event) and independently reverting the one-line change reproduces bug-1624 exactly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| settings | ||
| specs | ||
| steering | ||