superconfig/.github/workflows/ at c3fad32222eaae74f1c50bc068476867b7b8b679 · lass.pds.lassul.us/superconfig · Tangled

lass.pds.lassul.us / superconfig

0

This repository has no description

0

superconfig / .github / workflows

4 files

at c3fad32222eaae74f1c50bc068476867b7b8b679

Hermes .github.ci: hand the lazy store's fetch list from the eval job over 3d ago

.github.ci: hand the lazy store's fetch list from the eval job over In the benchmark run (PR 68) the neoprism job spent 29 s between fetching lazy-store and mounting: the dry-run for the paths to substitute (13 s in the shared job for the same machine) and their narinfo closure (the rest, 2,878 paths), both after the 21 s hestia prefetch of the drvs, which the dry-run needs. The eval job has the drvs and dry-runs the machines anyway for the shared derivations; it now keeps each machine's "will be fetched" list and uploads it with the shared ones. The machine job collects the closure of that list in the background while hestia prefetches the drvs, then mounts. Computing the closure in the eval job too would only move its time onto the eval job, before every machine job starts. For a single machine the eval job now dry-runs it (about 13 s), against about 29 s less in the machine job; with more machines the dry-runs ran already, and in parallel.

3 days ago

.github.hestia-gc: init Daily garbage collection of the hestia cache on the default branch, after hestia's own gc.yml, so ci.yml's cache stays within the 10 GB GHA cache quota.

3 days ago

unmaintained-graph.yml

ci: publish unmaintained-graph to GitHub Pages

2 weeks ago

update-pkgs.yml

.github.ci: build the NixOS machines on plain runners with hestia Replaces the farm call. eval evaluates the new ciToplevels output once with hestia's matrix subaction (the same machines the farm built: all nixosConfigurations), shared builds the derivations needed by more than one uncached machine once and hands the hestia manifest version with their outputs to the machine jobs, one job per uncached machine builds its toplevel by drv path. The ci job stays the required check; shared and the machine jobs are skipped when nothing is uncached. Every job pushes the store paths it added, built or substituted from hestia, to niks3 with its GitHub OIDC token, as the farm did, so deploys find the toplevels in cache.lassul.us. The niks3 client is the new packages.niks3 output. Measured on the ci-hestia-shared experiment with a nixpkgs bump: 15 min (eval 3.3, shared 3.3, 1-4 per machine) instead of 49 with the farm. No more queueing of runs for the farm.

3 days ago