Skip to content
Cockpit0.29.0
A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I2676

The build cache is verified and validated: failure paths, security and a real second-node hit

Where it stands

devtask.issue
Readiness
blocked 2 of its dependencies are not DONE
Status
BLOCKED
Can start
not now
Milestone
development-runtime
Milestone status
ACTIVE
Wave
3
Waiting on
I2673I2674
Holds back
none
Behind it in all
0
Evidence
0 of 2
In the waySubjectDetail
issueI2673I2673 is not DONE
issueI2674I2674 is not DONE

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I2676

majordomus plan verify I2676

majordomus plan done I2676

What it is

Objective
Prove the acceptance contract: stop the provider and build, restart and recover, bad credential, low space, put/get, remote hit across two nodes of one platform.
Why
The owner, 2026-10-13, with full clearance: set up MinIO, an sccache server and every mesh node, verified and validated. The cluster compiles the same Rust on every machine from a cold cache; two declared offload hosts were under their disk minimum that day. See ADR 0157.
Now
Measured on master b29cf4e487 on 2026-10-13: nothing is proved because nothing exists; the only candidate provider is unreachable over SSH.
Wanted
A case against a stub S3 for the failure paths, and a recorded run on real nodes for the hit, or a statement that two compatible nodes were not available; no cross-architecture claim.
Done when
unknown: the record declares no `completion`
Risk
unknown: the record declares no `risk`

Acceptance

  • With the provider stopped a build succeeds and the diagnostic names the cause
  • A restart recovers with no client edit
  • A bad credential gives an actionable message with no key in it
  • A second node's build hits what the first wrote, or the report says it could not be shown
Validation
bin/majordomus plan validateMJ_TEST_JOBS=2 bash test/run.sh 3013_a_mesh_build_cache
Evidence required
failure_path_casesecond_node_hit_recorded
Evidence present
unknown: the record carries no `evidence` entries

Scope

Touches
test/cases/3013_a_mesh_build_cache.shdocs/BUILD_CACHE.md
Not
Performance tuning beyond the recorded measurement
Depends on
I2673I2674
Priority
p1
Profile
implementation
Parallel safe
false
Owner
unknown: the record declares no `owner`

The work so far

Branches
none
Merged
none
Commits
0
Trunk
master
Sessions
none
Created
2026-10-13
Updated
2026-10-13
Started
unknown: the record declares no `started_at`
Verified
unknown: the record declares no `verified_at`
Completed
unknown: the record declares no `completed_at`

Synchronisation

Adapter
scripts/github-sync
Repository
unknown: the derived plan's header carries no repository
External issue
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there
unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.