docs(buglog): bug-1909 test-version-startup-consistency.sh fails on any dirty tree

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

2026-10-03 08:13:31 +00:00

2.9 KiB

Raw Blame History

status

status_updated

status_note

component

severity

timestamp

last_seen

occurrences

files

bug-1909: test-version-startup-consistency.sh scheduler check fails on any dirty tree (fingerprint vs -dirty)

Description

Observed:

FAIL [scheduler]: commit id MISMATCH ('ac7a4385-f4637557' vs 'ac7a4385-dirty')

src/tools/test-version-startup-consistency.sh compares the scheduler's --version commit id with the one in its startup log line. On a dirty working tree --version reports a content fingerprint (<sha>-<fingerprint>) while the startup log keeps <sha>-dirty, so the scheduler check fails.

Expected: the script passes on a dirty tree. The dirty-fingerprint feature keeps the startup log at -dirty on purpose (its own regression script, test-dirty-fingerprint-startup-log-unchanged.sh, asserts that), so the consistency check should compare the two forms accordingly (e.g. compare the base sha, or accept -dirty in the log when --version carries a fingerprint). Impact: the script can only pass from a clean tree; any developer machine with uncommitted changes (here .wolf/, .claude/, data/) sees a false failure. Test-only; product binaries behave as designed. Found by: spec task (controller-peers-env-fallback task 5.2)

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 @ ac7a4385-dirty
Deployment: n/a — the script builds and runs the scheduler locally, no cluster

Reproduction

From a working tree with any uncommitted change (e.g. echo x >> README.md in a scratch worktree at HEAD), run bash src/tools/test-version-startup-consistency.sh.
Observe FAIL [scheduler]: commit id MISMATCH ('<sha>-<fingerprint>' vs '<sha>-dirty').

Frequency: deterministic on any dirty tree (reproduced 2026-10-03 with HEAD's unmodified script in a scratch worktree with one README edit); passes on a clean tree.
Evidence: not kept (the script deletes its work dir on exit). Separately, the script's apiserver go build fails on this machine with "module lookup disabled by GOPROXY=off" (no Go module cache) — unrelated environment limitation.

Root cause

TODO: required for fixed/partial

Fix