lei.chen/myxce
1
0
Fork 1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

chore(wolf): checkpoint buglog.json (992 bugs)

Browse source
This commit is contained in:
Rongsong Shen 2026-08-21 06:47:59 +00:00
parent 502dd0230f
commit 340c5a83e8
No known key found for this signature in database
GPG key ID: 5BCDAAE0123E9FE2
1 changed files with 22 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

22
.wolf/buglog.json
View file

@ -17952,6 +17952,28 @@
],
"occurrences": 1,
"last_seen": "2026-08-20T21:10:00Z"
},
{
"id": "bug-1611",
"timestamp": "2026-08-21T15:10:00Z",
"error_message": "Discovered analyzing a real 108-session replay (xce_scheduler -i -s scheduler-replay-20260820-070103.replay, continue to EOF): sim_print_decision() (sim_loop.c) never printed a single DISPATCH or PREEMPT line across the entire replay -- only PEND -- even though 22 of the 30 jobs pushed at round 32 clearly transitioned to running (confirmed by ongoing JOB_UPDATE/JOB_RUSAGE ticks for jobids [0]-[21] every few rounds through round 107). An operator watching only decision output has zero confirmation those 22 jobs ever dispatched; they just silently stop appearing in PEND.",
"file": "src/scheduler/src/sim_loop.c",
"root_cause": "Not yet root-caused with certainty. Plausible, benign explanation: in --sim/-s REPLAY mode, jobs already resolved (dispatched) in the ORIGINAL recorded run may be replayed purely as state deltas (JOB_UPDATE/JOB_RUSAGE) without the live picker/allocator re-deriving a fresh XCE_DECISION_DISPATCH -- only jobs still outstanding (PEND) get freshly re-decided every round, which is why PEND is the only decision op ever observed. Unconfirmed against sim_loop.c's actual replay-vs-live-decide branching; needs a source read of how sim_loop.c distinguishes replayed-decision playback from freshly-computed decisions before concluding this is 'working as designed' vs a real visibility gap.",
"fix": "Not yet fixed. If confirmed benign (dispatch legitimately has no fresh decision object in replay mode), the round-summary rollup being designed for bug-1609/1610 should not label its dispatch count misleadingly (a permanent 'X dispatch' column reading 0 for an entire replay looks like a bug even when it isn't) -- consider deriving a running-job delta from info-jobs-equivalent state instead of the decision tally for replay-mode display. If NOT benign (a real decision-visibility gap), this is a separate, more serious finding than the formatting issues in bug-1609/1610.",
"tags": [
"repl",
"sim",
"replay",
"dispatch",
"decision-visibility",
"scheduler-sim-diagnostics"
],
"related_bugs": [
"bug-1609",
"bug-1610"
],
"occurrences": 1,
"last_seen": "2026-08-21T15:10:00Z"
}
]
}