3 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	2a86701891	buildstep: keep what one command of an ask writes into the caches for its later commands ... Every command of a check ran over the shared Go build cache beneath a throwaway tmpfs layer of its own, so the digests, the vet, the unit tests and the integration compile of one ask each compiled every package again. With Isolation.CacheLayer a command writes into a layer on disk of its own and Isolated moves it into the ask's kept layer when it ends; later commands read the kept layer above the shared cache, which stays unchanged (ADR 0541 §2, ADR 0448 §3). Empty CacheLayer keeps today's throwaway layer. Ported from feat/try-speed S2 (issue 1921).	2026-10-29 00:51:26 +01:00
jschoubben	8c3bfad86b	Run the run step's isolation proof only where bubblewrap is, under its own tag (issue 1309, S19, the lead's decision) ... The try's toolchain container has no bubblewrap; the checker runs the isolation tag on the build nodes, and merge-check.sh still vets it.	2026-10-22 18:06:10 +02:00
jschoubben	3b3cabd2b0	Prove a run step reaches no key, login, name or socket and leaves the caches unchanged (issue 1309, S19, ADR 0448 check)	2026-10-22 17:46:10 +02:00