docs(handoff): the rank-7 ownership probe ran — fresh PVC and fresh hostPath are indistinguishable, and the failure did NOT reproduce - #1182
Open
ZacxDev wants to merge 2 commits into
Open
Conversation
…s): fresh PVC and fresh hostPat
…s REFUTED: any nix invocation f
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Continues ci-speedup rank 7 (retry the devrc-ci node unpin). Two things landed: the perf baseline was re-taken, and the blocking ownership question was probed. Docs only.
1. The baseline was re-taken at
requests.cpu: 2claude/skills/tekton/reference/pipelines.mdstates the unpin's quoted wins are not re-derivable — pruned runs, measured atcpu: 4when live is2. Re-measured, n=31 gate TaskRuns:talos-xr6-r7p, 24/24)The upside survives the re-take — ~12.5 min at p90 is pure scheduling wait from pinning four nodes' demand onto one.
⚠
PipelineRuncreation→startTimeis median 0.0s and is a decoy: it reads as "there is no queue". The wait is entirely TaskRun→pod.2. The ownership probe — a NEGATIVE result
A hand-applied scratch Pod (not GitOps: no Flux, no
eventlistener.yamledit),ci-bulkpriority so it could preempt nothing, and it never mounted the livenix-store-cache. Two arms — freshlocal-pathPVC vs freshhostPath— both seeded with the gate's owncp -a /nix/. <vol>/.Every dimension came back identical:
600 root:rootbig-lock,755throughout,build-users-group=nixbld,sandbox=false,/buildabsent, buildsok, positive controlok.🔴 The failure did not reproduce on either arm. This extends the reference's already-REFUTED candidate 1 from "the volume ROOT's mode" to the whole tree — neither volume kind nor fresh-seed ownership is the variable, and
7839ef54's stated cause is less supported than before.Two blind spots, stated rather than folded in
nixos/nix:2.24.15ships nosu/setpriv/runuser/doas, soNIXBLD_CLIENT=NOT_MEASUREDon both arms./bin/shis static busybox with noid.v1 of the probe reported
NIXBLD_CLIENT=FAILED, which looked like a finding and wassu: command not found. Caught only by reading stderr rather than the label; v2 carries an explicit positive control and reportsNOT_MEASUREDinstead of a verdict.3. A correction to this doc's own earlier claim
It said the
privilegednamespace label "grants nothing". Half wrong: it grants nothing to the current gate, but hostPath admission depends on it —--dry-run=serveradmitted the probe's hostPath only because the namespace enforcesprivileged. Ranked items 5 and 7 are therefore coupled; reverting the label would block a hostPath retry at admission.Cleanup
Both probe pods, the cleanup pod and the probe PVC deleted;
nix-store-cacheverifiedBound 30Giafterwards. One empty dir remains at/var/lib/mnt/disk-1/nixlock-probe-hostpathontalos-xr6-r7p— recorded rather than left silent; removing it needs a pod mounting a shared disk's parent.devrc-ciwas never touched.