Commit Graph
219 Commits
Author SHA1 Message Date
aiongg ced652cd37 gate: first-party actions at the gate-setup repin (runner cargo home for rust-cache) (#322) 2026-11-22 01:04:28 -05:00
aiongg 8de85f814f gate: first-party actions at the gate-setup repin (WebDAV sccache on cluster runners) (#319) 2026-11-22 00:01:09 -05:00
aiongg e4a4048cb8 Merge the dry-run cache change 2026-11-20 04:14:21 +00:00
aiongg 2e04c2965b release, windows-arm64: install the toolchain the checkout's rust-toolchain.toml names
Part of storytold/photocraft#15711
2026-11-20 04:12:34 +00:00
aiongg e756744483 release: a dry run restores the caches and saves none
Part of storytold/photocraft#15711
2026-11-20 04:09:42 +00:00
aiongg 873bcb3de6 house-rules: accept the craft-agents block and add the generator
The check accepts the old house-rules blocks or one craft-agents block
(standards/app-agents.md, RFC-0072). write-agents writes or refreshes the
block from a craft-contrib commit on main and keeps text outside it.
2026-11-20 03:06:30 +00:00
aiongg ab4f427845 Merge pull request #297 from aiongg/gate-shard-archives
gate: shard-archives input, one test archive per shard
2026-11-19 18:37:46 -05:00
aiongg 94acf97a73 gate: trim a saving leg's cache entry to the build's units; first-party actions at the gate-setup repin
A leg that saves runs actions/cache-trim after its last build command (in the gate job, after the
artifact upload), before rust-cache's post step saves; it changes nothing unless the build recorded
its units in CRAFT_CACHE_UNITS, which actions/rust-cache sets only where the leg saves.
2026-11-19 23:19:14 +00:00
aiongg 9c45691f44 gate: shard-archives input, one test archive per shard
With archive-command and shard-archives: true, the build job sets NEXTEST_ARCHIVE_DIR,
NEXTEST_ARCHIVE_NAME and GATE_SHARDS, archive-command writes one archive per shard, and each is
uploaded as gate-archive-<os>-<k>. Shard k downloads only its own, so it fetches only the test
binaries it runs. One upload step per archive caps shard-archives at 8 shards; the select job
rejects more, and shard-archives without archive-command. Off by default: one archive for every
shard, as before.
2026-11-19 20:44:30 +00:00
aiongg 8341b41f55 gate: drop the prune-cache job; a called workflow's job permissions are checked at run start 2026-11-19 14:05:10 +00:00
aiongg ac2e87d47a gate: cache budget inputs (lint-cache, prune-cache) and a confined prune job; sonarcloud: build-cache input 2026-11-19 13:57:40 +00:00
aiongg a8fb24c80e gate: pin the shared actions to #290's merge commit 2026-11-19 13:39:04 +00:00
aiongg 528446563c gate: build the tests once per runner and keep workspace crates in a rolling cache entry
With archive-command, a build (<os>) job per runner builds the tests once
into a nextest archive; the shard legs download it and build nothing, and
only they wait for the build job. after-archive-command runs in the build
job after the upload. With cache-workspace-crates, the saving leg writes a
rolling dependency entry that keeps the workspace crates, and every leg
restores the newest one with restore-mtimes. The lint legs move to a lint
job of their own that never waits for the build. Every job's setup is
actions/gate-setup; commands run through actions/gate-run. Every new input
defaults to today's behaviour.

The save-condition guards read the cache-save and writes inputs every job
passes to gate-setup: the build and lint jobs carry the approved condition,
the gate job the same narrowed to its one saving leg per runner.

Result markers are files named after their leg and download with
merge-multiple, so one shard or one build lands where the check reads it.
The archive upload overwrites on a re-run. archive-command without
test-shards is an error.

The first-party actions are pinned to the commit that added gate-setup.
2026-11-19 09:30:18 +00:00
FredApps 2c06746765 ci: pin nested shared gate actions to reviewed revision (#289) 2026-11-19 13:34:26 +07:00
FredApps 139cccb97f ci: pin native runner fixture to production Rust 1.100.0 (#288) 2026-11-19 13:10:45 +07:00
FredApps 438b785997 ci: validate native Cargo runner semantics with tiny fixtures (#287)
* ci: validate native Cargo runner semantics with tiny fixtures

* test: separate doctest runner context without weakening allowlist
2026-11-19 13:02:16 +07:00
FredApps 5e475d5d1e ci: audit implicit-host FreeBSD runtime planned-unit reuse (#286) 2026-11-19 12:46:00 +07:00
FredApps a44bf91fb5 ci: measure planned FreeBSD prebuild target projection without compiling (#285) 2026-11-19 12:33:12 +07:00
FredApps 0be61baefd ci: measure native bootstrap while preserving workspace features (#284)
* ci: guard a bounded native geometry measurement with exact planned closure

* ci: preserve workspace features while measuring native browser bootstrap
2026-11-19 12:20:14 +07:00
FredApps b5c6f5913e ci: compare planned Photo units on native FreeBSD without builds (#283)
* ci: compare planned Photo units on native FreeBSD without builds

* ci: verify transferred source without overriding Git ownership guard
2026-11-19 11:59:33 +07:00
FredApps cccebf20a1 ci: compare pinned Photo resolved features without builds (#282) 2026-11-19 11:43:25 +07:00
FredApps dbe0fbf6af ci: inventory pinned Photo targets without building (#281) 2026-11-19 11:34:22 +07:00
FredApps 2317dca7b2 test(ci): prototype bounded libtest subprocess fixtures (#280) 2026-11-19 11:01:46 +07:00
FredApps 21a58ac409 ci(freebsd): measure bounded complete target toolchain setup (#279) 2026-11-19 10:44:00 +07:00
FredApps 9fe0627fb4 ci(freebsd): add bounded verified-download diagnostic 2026-11-19 04:01:00 +01:00
FredApps 2261f42f01 Merge current main for combined short-suite validation 2026-11-19 03:46:15 +01:00
FredApps fa34e3106d fix(freebsd): preserve and isolate cross-target Cargo caches 2026-11-19 03:42:06 +01:00
aiongg c5f8dc3b74 Merge pull request #275 from aiongg/ci-cache-name-strip
gate: cache-name and dev-strip inputs; manual Windows build diagnostic
2026-11-18 21:30:33 -05:00
FredApps c0e799e2a0 fix(freebsd): bound release-file download retries 2026-11-19 03:23:37 +01:00
aiongg 6b0c83fa60 gate: cache-name and dev-strip inputs; manual Windows build diagnostic
cache-name gives each call of the gate in one job its own dependency-cache entry (gate-<name>); the default keeps today's key. dev-strip builds the test profile without debug info and strips symbols.
2026-11-19 02:21:58 +00:00
FredApps 204c556c5f Merge main and preserve artifact uploads on validated producers 2026-11-19 01:28:57 +01:00
aiongg 112ef59c08 gate: each shard leg records its latest status, so a re-run that fails replaces an earlier pass 2026-11-18 20:20:21 +00:00
aiongg 29d68afad0 gate: test-shards runs each runner's tests as N shard legs
With test-shards N > 0, the gate leg of each runner becomes N test <k>/<N>
(<os>) legs. Each has the full setup, restores the gate's Rust cache entry and
runs shard-command (windows-shard-command on Windows) with GATE_SHARD,
GATE_SHARDS and NEXTEST_PARTITION (hash:<k>/<N>) set, building and running
its share of the tests. Shard 1 saves the cache by the gate leg's rules (the
warm leg saves instead when there is one); the others only restore. lint and
cache warm legs run once per runner. A gate (<os>) job passes only when every
shard of that runner passed, from per-shard pass markers.

test-shards defaults to 0, which leaves every existing call as it was.
2026-11-18 19:09:44 +00:00
aiongg ea2e684a31 rust-cache: Swatinem v2.9.3 by commit; cache-version v2
StepSecurity's v2.9.1 cut every target/<profile>/build entry at its last '-',
so Cargo's new build-dir layout (build/<package>/<hash>/) lost most dependency
packages from each saved entry. v2.9.3 checks the exact name first (#371 there)
and keeps the Windows path fix (#355 there) that v2.9.1 was pinned for.

The cache-version default moves to v2 once: rust-cache never replaces an
exact-key entry, so the pruned v1 entries would otherwise be restored as they
are until the lockfile changes.
2026-11-18 18:54:00 +00:00
aiongg 13d451f0e6 Merge pull request #270 from aiongg/cache-after-build
gate: native-only cache key and an optional cache-warm leg
2026-11-18 09:50:08 -05:00
FredApps 42e99d3762 ci(freebsd): allow bounded compilation concurrency 2026-11-18 15:42:03 +01:00
aiongg a24d4fc3de gate: cache key from native profiles only, optional cache-warm leg saves after the build
The rust-cache key hashes the root [profile] tables except wasm-only ones (web, wasm-*), so a
web-profile edit no longer starts every native cache cold. A new warm-command input adds a
default-branch leg that runs only the build and saves the gate entry as soon as it succeeds,
instead of after the tests.
2026-11-18 14:14:58 +00:00
FredApps 96108275db Avoid worktree resync in read-only guest diagnostics 2026-11-18 12:41:06 +01:00
FredApps 3dba51aeae ci(freebsd): capture bounded resource evidence after failures 2026-11-18 12:38:19 +01:00
FredApps 6c1714ff04 fix(freebsd): reclaim hosted toolchains before VM allocation 2026-11-18 10:13:28 +01:00
aiongg efe146ee91 gate: key the caller cache on files too (cache-key-files)
A caller that keeps its pins in the fetch script names it in cache-key-files, so
the pin is written once and a new pin or fetch starts a new entry. The key is
computed once and used by both the restore and the save.
2026-11-17 18:57:53 +00:00
aiongg cd0795f15d gate: run platform legs on a pull request only when it can change them (select-os)
A select legs job (actions/select-platforms) runs the select-os legs on a pull
request only when a changed file is in a crate with platform cfg code or a crate
that depends on one (cargo metadata --no-deps and a scan of the sources), is part
of the build setup or select-paths, or lies outside every crate and is not
documentation. The select-label label (full-ci) and every other event run every
leg. Without select-os no select job runs and the matrix is os, as before.

On craft-libs today 37 of 177 crates have platform cfg code and 57 are affected
with their dependents; 39 of the last 80 merged pull requests would have run the
Linux leg only.
2026-11-17 18:55:31 +00:00
aiongg f8f8952237 gate: cache the data the caller's setup fetches (cache-paths, cache-key)
The cache-extra-paths item of #212. The paths are restored before setup-command
and saved after it under the dependency cache's save rule, one entry for every
OS, keyed on the caller's pins. craft-libs uses it for the PhotoCraft PSD corpus,
which otherwise builds PhotoCraft's xtask on every leg (1:51 on Windows).
2026-11-17 18:53:15 +00:00
aiongg 7d989465c1 gate: lint legs beside the test legs (lint-command)
With lint-command set, each runner in os gets a lint (<os>) leg that runs the
lint checks with the same setup, so clippy no longer runs before the test build
on the critical path. One job definition with a part matrix dimension; the test
part keeps the gate (<os>) check name, and the lint part has its own rust-cache
entry. Empty lint-command keeps today's behaviour.
2026-11-17 18:52:39 +00:00
Ephraim 42e79d293e gate: optional artifact upload 2026-11-16 19:00:57 +02:00
Martin BallandClaude Opus 5.5 f9e835af4f fix(rust-cache): pin v2.9.1 so Windows jobs save their cache (#249)
step-security/rust-cache v2.9.2 ships an ES-module bundle. Its bundled
minimatch 3 calls require('path'), which throws in an ES module, so it
falls back to '/' as the separator. On Windows no cache path then
matches and every save fails with "Path Validation Error". Windows legs
never saved a cache and built every dependency from scratch.

v2.9.1 is a CommonJS (ncc) bundle with the same inputs. Pin it
everywhere rust-cache is used and add a test that keeps every pin on
the action's commit and off v2.9.2.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FypgCXtSjB6e5jmy9Uq7u8
2026-11-16 12:19:03 +00:00
Martin Ball 59d1ecc4ea Fix shared cache save policy and target paths (#253)
Disable Rust cache saves after failed runs and resolve CARGO_TARGET_DIR relative to the checkout. Use dated FreeBSD cache entries and skip a matching same-day save. Keep inherited-target tests independent of the caller environment.

Contributor: @benandez.

Validated with the passing hosted test job, 95 focused passes plus one existing csh skip, and four inherited-target tests. Native Windows/FreeBSD VM and live cache-service execution were not claimed.
2026-11-15 19:19:40 -06:00
FredApps 5b4eeb2323 fix(freebsd): fail closed if the aarch64 job has no CARGO_BUILD_TARGET
The 15 November scheduled dry-run wrote x86_64 archives in the aarch64
job because an unset PKG_CONFIG_PATH in the cross env heredoc left
CARGO_BUILD_TARGET unset, and FreeBSD sh did not abort. #242 already
stops the heredoc from expanding that unset variable. This checks that
the env file actually exported the target, and that the build and
package steps still have it, so a similar miss fails before packaging.
2026-11-15 12:17:00 +01:00
Dylan M. Taylor c8f4b6ec2a fix(freebsd): include shared pkgconfig metadata in aarch64 sysroot (#247)
* fix(freebsd): include share pkgconfig in cross sysroot

* test(freebsd): cover share pkgconfig sysroot paths
2026-11-14 23:03:20 -05:00
Dylan M. Taylor 831527c68a fix(freebsd): include X11 protocol metadata in sysroot (#245) 2026-11-14 22:20:46 -05:00