From 50f8a2a59fa129fd982c4245f4b00adb9aff9188 Mon Sep 17 00:00:00 2001 From: wjarvis mos-comms Date: Fri, 17 Jul 2026 12:56:38 -0500 Subject: [PATCH] comms: usc 20260717T175638Z --- comms/20260717T175638Z__from-usc__18612650.md | 7 +++++++ 1 file changed, 7 insertions(+) create mode 100644 comms/20260717T175638Z__from-usc__18612650.md diff --git a/comms/20260717T175638Z__from-usc__18612650.md b/comms/20260717T175638Z__from-usc__18612650.md new file mode 100644 index 0000000..a818c2e --- /dev/null +++ b/comms/20260717T175638Z__from-usc__18612650.md @@ -0,0 +1,7 @@ +--- +from: usc +to: all +utc: 20260717T175638Z +--- + +from: usc / to: homelab — #815 @ade931a5 CI 1889 root cause diagnosed (not fixture): ONLY failure is test-pr-diff-context.sh line42 `git: command not found`; all vitest GREEN. ci-base (node:24-alpine, Dockerfile.ci) bakes python3/make/g++/postgresql-client/bash but NOT git; the hermetic fixture legitimately needs the git binary. Fix path A (house style, Dockerfile comment prefers baking over per-run apk add — precedent bash/pg-client): SEPARATE prerequisite PR adds `git` to the apk add line in Dockerfile.ci -> merge main -> ci-image.yml rebuilds ci-base:latest with git (~25min) -> rebase #815 -> green. Cannot fold into #815 (image only rebuilds on main push touching Dockerfile.ci, so PR can't self-verify). Alt B = per-run `apk add git` in ci.yml test step (self-contained/faster but against the documented bake convention). Proceeding with A inside my #795 lane (same worker, sequential — stays <=2 agents); the infra PR gets its own exact-head RoR + your merge GO. Flag: this adds a prerequisite infra PR to the #795 sequence. Object/prefer B? Else I drive A. #818 unchanged (REQUEST CHANGES 17959, ms-792 on gap-a).