myxce/.wolf/bugs/bug-1938.md
Rongsong Shen 2fed7a6e5f
docs(buglog): log P0 defects from the 2026-10-10 review (bug-1936..bug-1952)
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-10 08:15:28 +00:00

2.3 KiB

id status status_updated status_note component severity timestamp last_seen occurrences files tags related
bug-1938 open 2026-10-10 newly logged scheduler wrong-result 2026-10-10T08:14:41Z 2026-10-10T08:14:41Z 1
src/scheduler/src/core.c
src/scheduler/src/plugins/builtin_fcfs.c
scheduler
queue
admin-control

bug-1938: xce_scheduler dispatches jobs from closed or inactive queues (queue readiness gate is a stub)

Description

Observed: (source reading, .kiro/reviews/project-gap-review-2026-10-10.md (P0); to be confirmed by a failing test before the fix) The admin queue controls set and clear the closed/inactive flags (src/controller/queue.c:131-152), but the scheduler's gates always pass:

/* FIXME this is just stub, we need to add more */
int sched_job_is_ready(xce_sched_job_t* j) { return 1; }
/* FIXME this is just stub, we need to add more */
int sched_queue_is_ready(xce_sched_queue_t* q) { return 1; }   /* core.c:646-649 */

Expected: Jobs of an inactive queue are not dispatched (they stay pending with a reason); a closed queue accepts no new submissions. Impact: Admin queue control silently ignored: inactivating a queue does not stop dispatch. Found by: review: .kiro/reviews/project-gap-review-2026-10-10.md (P0)

Environment

  • OS: no /etc/os-release; Docker container; NixOS kernel; kernel Linux 6.18.33 x86_64
  • libc: glibc 2.42-47 (interpreter /nix/store/wb6rhpznjfczwlwx23zmdrrw74bayxw4-glibc-2.42-47/lib/ld-linux-x86-64.so.2)
  • Toolchain: gcc (GCC) 15.2.0, meson 1.9.1
  • Build: asan (xce.build)
  • Code: scheduler-framework @ 94472ee3-dirty
  • Deployment: any (found by source reading; the failing test that confirms it is named in Verification)

Reproduction

  1. Deploy a cluster, inactivate queue normal (queue control), submit a job to it.
  2. The job is dispatched and runs.
  • Frequency: deterministic (by code reading; confirmed by the RED test of the fix)
  • Evidence: the code sites quoted in Description; no logs kept.

Root cause

TODO: required for fixed/partial

Fix

TODO: required for fixed/partial

Verification

  • Test: TODO: name + file; RED before the fix, GREEN after
  • Suites: TODO: suite results and build profile
  • Live: TODO: soak/deploy run, or n/a and why

References

  • Related: none