Rongsong Shen
c454f0652d
test_info_job_reports_state_queue_priority now expects "Tasks: min = 1, max = 1" instead of the pre-fix "min = 0, max = 0" incidental byproduct (a fixture's parse_select() failing on an unregistered "type" resource used to leave the primary's task-count fields at memset-zero; apply_job_task_count() now correctly overwrites them to the job's real submitted default of 1/1). This was the one deferred item tracked in tasks.md's Implementation Notes since task 2.1. Full-suite regression confirmed clean: scheduler/controller/worker suites pass except the pre-existing, unrelated bug-1758 (predates this feature, attributed to a separate spec). A full /xce-build all also surfaces bug-1723, a pre-existing lib-suite fixture-teardown leak dating to before this feature and outside Requirement 5.1's named scope (scheduler/controller/worker) -- confirmed untouched by any of this feature's commits. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XYdtrEWWZfKRRGED7raEYg |
||
|---|---|---|
| .. | ||
| settings | ||
| specs | ||
| steering | ||