Repository navigation
fix(ci): pin drills-nightly to nself-ci 1.2.11 (D-1090) - #462
Merged
Merged
Conversation
…(D-1090) The nightly failed at its first step because CI_VERSION, CI_RELEASE_URL and CI_RELEASE_SHA256 were empty placeholders. v1.2.11 is the pin nself-ci.yml already runs green; sha256 checked against the release asset digest.
…0, D-1093) - drills-nightly: Go, docker/podman and gVisor runsc set up as in ci-isolation-linux; nself-ci on PATH; read-only GH_TOKEN, checks/statuses read; run store kept and job logs uploaded - nself-ci-source: --trust owner for a head in this repository (a PR merge ref is untrusted otherwise, E625) - toolchain-pins: one compact JSON line (E640); ghcr.io images resolve like docker.io - truth-sweep: list public repositories anonymously when no token reaches the drill - security-suite/mutate.sh: copies see the sibling forgejo and github-runner plugins, so the baseline is green - boundary test: agent/update/source.go may import net/http (same release fetch as agent/install) - blob rig: warm-up with a frame that does not fail the route (TestE14BlobAnnouncementForms was racy)
…(it no longer applied)
…and the isolation drill (E625 on PR merge refs)
…) and the newest Go 1.26; isolation drill excerpt names the failing assertion
…owner on dispatch)
…d-only token through its config file
…est; dispatch of ci-isolation-linux is the owner's run
…ds its 200 commit read)
…rivate TMPDIR blocks job users)
…users cannot enter the private run store)
…can; the android planner test ignores the runner's ANDROID_SDK_ROOT
…whole grace period on Linux The executor waits out the grace period after the job leader exits while any remembered descendant is alive. On Linux an orphan is adopted by the agent (subreaper) and stays a zombie until reaped, and a signal-0 probe succeeds on a zombie, so every cancel of a job that had a background child waited the full 10 s grace before reporting its result, past the coordinator's 5 s cancel timeout. Alive now means not a zombie, the orphans are reaped while waiting, and the wait ends as soon as the group is gone. The runs follow tests also stop depending on the host's container runtimes: reading a run recovers after dead coordinators, which runs docker info and ps, about a second on a CI runner with a live daemon.
…e; audited gate process starts join the exec-funnel allowlist
…(the network leg passes with the default)
…aStops gets room for a loaded runner; keep the isolation drill output
…e the isolation drill
…bel method (hygiene and sweep failed with exit 125 and left job networks behind)
…ile the engine's probe container winds down
…s own probe container to exit
…le-job run is a partial selection and exits 1)
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.
drills-nightly has failed at its first step since it was added: CI_VERSION, CI_RELEASE_URL and CI_RELEASE_SHA256 were empty placeholders ("CI_VERSION is not set in this workflow's env block", run 39925845774).
The three values now equal the pin nself-ci.yml already runs green (v1.2.11, linux-amd64). The tarball sha256 matches the release asset digest (checked by download). A workflow_dispatch run of this branch (39952456795) passed the pin, checkout, install and nft steps; the pipeline step is the nightly drill itself, whose red/green is the freshness signal (D-0051, P7-PLUG-35).