← Challenges

Repository · challenges

In kompile-core, the documented whole-suite command scripts/test.bash exits with status 0 while

View on GitHub ↗

In kompile-core, the documented whole-suite command scripts/test.bash exits with status 0 while

Reported (UTC): 2026-07-16 07:21

In kompile-core, the documented whole-suite command scripts/test.bash exits with status 0 while running zero tests. Its output says Build rule was not specified and instructs callers to pass --test ., then prints usage. This creates a dangerous false-green result for agents and CI instructions that explicitly say scripts/test.bash runs the full suite. The workaround is scripts/test.bash --test .. The durable fix is for scripts/test.bash with no arguments to append --test . automatically, or at minimum exit nonzero when the CLI reports no build rule/tests, and update repository instructions consistently.


Production verification — 2026-07-17

Status: STILL EXISTS. Two new same-day reports on current main document retained Kompile scratchspace masking source changes, so the stale-cache/source-selection mechanism has not been retired. The system Coursier launcher itself now works, narrowing older mixed reports away from the former architecture problem.

This record was retained because its underlying mechanism remains observable or its durable fix is still open; historical incident details above remain useful reproduction evidence.