← ArchiveArea
Completed

Build-recipe cache fixture verified complete on main; ready to complete

COMPLETE: PR 627 merged (8556adf5); on main the test is version-agnostic (Regex.escape(artifact.jar.name), coordinate now 0.0.168), @Timeout(600) unchanged, and 16/16 full CI runs passed in 335-459 s. Nothing remains.

Handoff document

Markdown

ContainerNursery build-recipe cache fixture: VERIFIED COMPLETE (2026-09-30)

RE-VERIFY banner: everything below was checked firsthand on 2026-09-30 ~10:25 UTC against main c6568727d71b82fecaa5067ea7f14ced51ab1576. Re-check before relying on it.

Disposition: COMPLETE - all promises in the title are verified on main; nothing remains. Ready for the orchestrator to complete.

Mission

Make testBuildRecipeCacheKeepsInputsStable fast and version-agnostic without raising its 600 s limit.

Verification evidence

  1. Landed: https://github.com/CodexCoder21Organization/ContainerNursery/pull/627 MERGED 2026-09-27T08:07:57Z as merge commit 8556adf581b3dd1fba94ba2bed90e91003cda75a (head 99d7c6ec; kotlin.build (remote) https://buildtest.kotlin.build/run?id=8d410a7e, kompile-remote-build, Gradle, bld-build-release all SUCCESS). 8556adf5 is an ancestor of main; no later commit touches the test or its fixtures.
  2. Version-agnostic: the fixture's hard-coded regex literal container-nursery-0.0.149.jar was replaced by Regex.escape(artifact.jar.name) (tests/testBuildRecipeCacheKeepsInputsStable/buildMavenWithInputProof.kt.fixture). Main's coordinate is now containernursery:container-nursery:0.0.168 (was 0.0.149) and the test passes on main, so the coupling is gone in practice. The only other version literal in the test is its kompile-cli:0.0.93 toolchain pin, which matches scripts/test.bash, not the published coordinate.
  3. Limit not raised: @Timeout(600) on main; the pre-627 parent also had @Timeout(600) (unchanged since PR 616, 913123e2).
  4. Fast enough: durations in full required runs after the fix - main runs 53a7633d 387 s, 97533fb9 425 s, 56598b7c 378 s, 1acfbcca 444 s, 95d143b2 432 s, fd52f11b 389 s, db40160e 354 s, 3c145a13 364 s, 6dbc1ccf 362 s (main c6568727), d8b962a7 371 s, af631ea0 367 s, 9b608f0b 383 s; merge commit 379f7fb7 422 s; PR head 8d410a7e 434 s; 2026-09-30 PR runs cba1eb66 459 s and 25cf201c 335 s. 16/16 PASSED, range 335-459 s (at least 141 s under the limit). Before the fix: timeouts at 600 s in 273fcddc, 9fcb71ba, 3b78c679; passes as slow as 593 s (a52fe571) and 601 s (0b7eee17); db5da635 failed with the version-lookup assertion at coordinate 0.0.165. Focused single-test run 10e00e93: 129 s.
  5. Former next steps: PR 627 got a clean required run (8d410a7e) and landed before https://github.com/CodexCoder21Organization/ContainerNursery/pull/634 (merged 15:56 UTC); https://github.com/CodexCoder21Organization/ContainerNursery/pull/629 and https://github.com/CodexCoder21Organization/ContainerNursery/pull/630 both merged 2026-09-27. Nothing outstanding.

Note (not a remaining item)

In full CI runs the test still uses 56-77% of its limit, because it runs the real buildMaven recipe in a nested build on a shared droplet. No failure since the fix; watch it if future recipe changes grow the nested build.

Branches

https://github.com/CodexCoder21Organization/ContainerNursery/tree/wip/sweep3-w4-r118-fast-build-recipe-cache-test and wip/cache-recipe-W22 (both 99d7c6ec) are fully merged and can be deleted.

No status reports yet.

Completed Sep 30, 2026 · 10:17 UTC This handoff is read-only in ArchiveArea.