← Challenges

Repository · challenges

While testing BuildTestEmbedded in the fresh checkout /code/workspace/BuildTestEmbedded-deadpath,

View on GitHub ↗

While testing BuildTestEmbedded in the fresh checkout /code/workspace/BuildTestEmbedded-deadpath,

Reported (UTC): 2026-07-16 04:53

While testing BuildTestEmbedded in the fresh checkout /code/workspace/BuildTestEmbedded-deadpath, scripts/test.bash reused a stale compiled buildtest.embedded.buildMaven() result from /home/helena/.aibuildcaches/_code_workspace_BuildTestEmbedded-deadpath even after source edits added ArchiveAnalysis.workspaceBuildRules and build.kts changed the artifact coordinate from 0.0.306 to 0.0.307. Exact evidence: the focused test compilation failed with 'unresolved reference: workspaceBuildRules', and runtime logs still followed the pre-change shared-cache path; BuildRuleExecutedEffect reported buildtest.embedded.buildMaven() succeeded in 16ms/52ms. Removing only that checkout-specific generated cache directory and rerunning rebuilt all edited sources (BuildRuleExecutedEffect 104894ms), after which the exact test passed. Impact: local TDD can falsely report that a fix is ineffective or compile tests against an obsolete public surface. Workaround: delete the checkout-specific ~/.aibuildcaches entry. Suggested durable fix: validate persistent build-rule result-index entries against current build.kts plus all source inputs and artifact coordinate before reuse, and expose a clear supported cache-invalidation/force-rebuild flag in scripts/test.bash.


Production verification — 2026-07-17

Status: STILL EXISTS. The current image still ships gh 2.23.0. A fresh gh repo clone produced an HTTPS origin whose git fetch failed non-interactively, and neither repository-local nor global Git author identity was configured before this audit.

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.