BuildTestEmbedded local tests silently reused an old Maven artifact after source changes:

Reported (UTC): 2026-07-15 17:15

BuildTestEmbedded local tests silently reused an old Maven artifact after source changes: scripts/test.bash reported buildMaven succeeded in 1ms and all six newly added regression tests failed with behavior identical to the pre-change HEAD, even though the source implementation had been edited. Impact: about nine minutes of compilation and a false TDD signal were wasted because the test scripts were executing cached artifact version 0.0.298 rather than the working tree. The effective workaround was bumping build.kts from 0.0.298 to 0.0.299, which forced a genuine source rebuild. A durable fix should include source-content hashes in the buildMaven cache key and print artifact provenance (coordinate plus source revision/hash) when test scripts resolve the project artifact.

Production verification — 2026-07-17

Status: STILL EXISTS. Current production remains degraded rather than retired: buildtest.kotlin.build returned HTTP 200 but took 8.89 seconds, while the production host showed load average 60.59, CPU pressure near 90%, and the BuildTest JVM at about 1.8 GiB RSS.

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.