Rongsong Shen
d26ff8870d
The buglog was one 27K-line JSON file whose fields covered only symptom,
root cause and fix, as free text: 2% of entries named the code version a
bug was found on, 12% the build profile, 36% a way to reproduce, and 58% of
the file was OpenWolf hook auto-detections ("Missing guard clause",
"Function not marked async" on .md files).
- .claude/skills/buglog/bug-record.md: the record standard. Eight
sections (Summary as the title, Description, Environment, Reproduction;
Root cause, Fix, Verification, References once fixed), each with the
content it must contain -- e.g. Environment needs the OS, the libc the
failing binary loads (from its ELF interpreter: glibc 2.42 in the nix
shell vs 2.40 on the host), toolchain, build profile and commit.
- .wolf/bugs/<id>.md: 500 records migrated from buglog.json; every field
verified to round-trip. They carry legacy: true and an explicit "not
recorded" where the old log had no such field; component derived from
file paths, severity from keywords (else unknown), fix_commits from
hashes in status_note/fix that git resolves (91 of 463 fixed).
- .wolf/buglog-archive.json: the 710 hook auto-detections, verbatim.
- .wolf/buglog.json is now an index generated from the records, keeping
the fields OpenWolf's hooks and `openwolf bug search` read.
- scripts/buglog.py rewritten: new (template + Environment collected from
the machine and --binary), check, status (refuses a status the record
doesn't support; fixed needs Root cause, Fix, Verification and
--commit hashes git resolves), note, recur, set, show, list, triage,
env, index. 29 unittest cases in scripts/tests/test_buglog.py.
- scripts/git-hooks/pre-commit runs `check --staged`: incomplete staged
records, a legacy record hand-changed to fixed without the fix-time
sections, a new record claiming legacy: true, or a stale index refuse
the commit.
- scripts/gitea-sync.py reads the records: issue body = the record's
sections plus linked fix commits (origin remote, GITEA_COMMIT_REPO to
override), and a body hash so an issue's text is refreshed when the
record changes.
- bug-1866 rewritten to the full standard as the worked example.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2.2 KiB
| id | status | status_updated | status_note | component | severity | timestamp | last_seen | occurrences | files | tags | related | legacy | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bug-1559 | fixed | 2026-09-24 | scheduler | unknown | 2026-08-15T13:10:00Z | 2026-09-19T09:00:00Z | 1 |
|
|
|
true |
bug-1559: xce-build.sh scheduler's RUN_TESTS block never builds or runs the 4 new…
Description
xce-build.sh scheduler's RUN_TESTS block never builds or runs the 4 new component-failover-adoption task-3.x scheduler test binaries (sched_scheduler_connect_test, sched_scheduler_backpressure_test, sched_scheduler_decision_publish_retry_test, sched_scheduler_decision_redelivery_test) -- it only builds/runs 'xce_scheduler sched_test'. They only got compiled in this session as a side effect of a separate worker build and had to be run directly, bypassing the canonical script.
Environment
Not recorded (migrated from buglog.json).
Reproduction
Not recorded (migrated from buglog.json).
Root cause
xce-build.sh's scheduler case's RUN_TESTS list was never updated when task 3.x added 4 new standalone test executables under src/scheduler/testsuite/meson.build -- same class of gap as bug-1558 (documented commands cover only a subset of the real suite), just for the scheduler component instead of apiserver's CGO path.
Fix
FIXED (component-failover-adoption tasks.md Phase 6, non-blocking build-tooling fix). src/tools/xce-build.sh's scheduler case's RUN_TESTS block now runs meson test -C "$BUILD_DIR" --suite scheduler --print-errorlogs instead of invoking sched_test directly by path -- meson test rebuilds by default, so no need to separately enumerate the 4 previously-skipped binaries. Verified 2026-08-15: xce-build.sh scheduler asan now runs all 41 scheduler suite tests (was: 1 binary only). NOTE: running the full suite for the first time surfaced a previously-invisible failure, test_recordstart_symlink_escape_replies_error (test_admin_request.c) -- logged separately as bug-1560, unrelated to this fix or to component-failover-adoption.
Verification
Not recorded (migrated from buglog.json).
References
- Related: bug-1558