From 054974c3fb4ef2e326c44cfad5d9736474ff82ea Mon Sep 17 00:00:00 2001 From: Jeroen Schweitzer Date: Sun, 9 Aug 2026 15:56:21 +0200 Subject: [PATCH] ci(make): reserve exit 69 for "could not run" (D-26) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Environment guards now exit 69 rather than 1, so a caller can tell a suite that could not start from one that ran and failed. The first toj test sweep reported "3 repositories failed" and none of the three had executed a test — two could not find go, one had no venv. That points the reader at the tests when the fault is in the environment. Only the environment guards change. A gitleaks finding, a failed test run and a vulncheck hit still exit 1, because those did run and did fail. Co-Authored-By: Claude --- Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile b/Makefile index fdec8d1..13d999f 100644 --- a/Makefile +++ b/Makefile @@ -23,7 +23,7 @@ setup: ## Create the venv and install the test extra .PHONY: test test: ## Run the test suite - @test -x $(VENV)/bin/python || { echo "FAIL — no venv in this tree; run: make setup"; exit 1; } + @test -x $(VENV)/bin/python || { echo "FAIL — no venv in this tree; run: make setup"; exit 69; } $(VENV)/bin/python -m pytest tests/ # No `lint` target, deliberately. CLAUDE.md states it outright: no linter is