Rongsong Shen
38d9fe3583
Discovered during live manual verification of scheduler-sim-diagnostics Requirement 6 (human-readable info limit formatting) against a real deployed cluster with a real captured replay. A mem-based limit (limits2/ug1_global_mem/night_mem_pct) never shows a live usage instance even when its matching job is genuinely dispatched with an intact rusage[mem=...] reservation -- while a slots-based limit (limit1) in the same replay correctly populates one. Suspected timing/ ordering gap between WORKERS_PUSH replay-event application and match_job_global_limit_()/match_job_host_limit_()'s resmgr lookup, not confirmed. Out of Requirement 6's boundary (display-formatting only, proven correct independently) and out of bug-1826's already-closed scope (matching invocation itself, not this resource-type-specific timing gap). Needs its own dedicated investigation. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RLSNJhNoULvVcUhXEFafQC |
||
|---|---|---|
| .. | ||
| hooks | ||
| .gitignore | ||
| _scan-state.json | ||
| anatomy-index.json | ||
| anatomy.md | ||
| buglog.json | ||
| cerebrum.md | ||
| config.json | ||
| cron-manifest.json | ||
| cron-state.json | ||
| memory.md | ||
| OPENWOLF.md | ||
| reframe-frameworks.md | ||
| STATUS.md | ||