chore(scheduler-allocator-runner): validation passed; new_requirements item 4 resolved (task 5.2)
Clean ASAN scheduler suite 96/96 with no expectation changes in existing tests beyond wiring; scheduler invariant audit of the allocation path clean (driver state-equivalence, core I/O isolation, picker/allocator rendezvous, snapshot parity). issues/new_requirements.md item 4 marked resolved. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
d006de3853
commit
bf0ba68b22
2 changed files with 4 additions and 1 deletions
|
|
@ -110,6 +110,8 @@ we prefer to make jobinfo to also show resreq and pending reason information and
|
|||
|
||||
According the design of scheduler-allocation project we can make a general allocation function in plugin framework to make sequential and parallel allocation plugins do not need to export my_alloc().
|
||||
|
||||
Resolved (2026-09-30): see `.kiro/specs/scheduler-allocator-runner/`. The framework routine `sched_allocator_run()` (src/scheduler/src/alloc_runner.c) is now the single allocation entry point (`job_alloc_fn`) for both allocator plugins; seqjob and parjob supply only their policy via `allocator_iface` (plan generator, optional acceptance guard), and both private `my_alloc()` routines were removed.
|
||||
|
||||
5. Enhance controller to clean up jobs which meet following conditions:
|
||||
- pre-defined parameter in cluster configuration for how long to keep a job before it can be clean uped
|
||||
- Job is completed until not exceed a period (say job clean up period)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue