From d888cc570277068923d55a9d8f10ae4fc8f423ff Mon Sep 17 00:00:00 2001 From: Hanif Koh Date: Fri, 4 Sep 2026 21:19:26 +0800 Subject: [PATCH] ci: print the override sweep's stage summaries in the job log pytest captures stdout on passing tests, so the per-stage summaries the sweep prints never reached the log and the job summary said "no stage summaries" on every green run. Combined with continue-on-error, that meant a shard reporting zero effective options looked identical to a healthy one unless you downloaded the artifact and read the JSON. -rA prints them, which matters more now that the effect stage reports a per-fixture breakdown and a no_baseline bucket for a fixture that would not slice. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01TSynfTLvSnHBbVkRUm56nY --- .github/workflows/cli_overrides.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.github/workflows/cli_overrides.yml b/.github/workflows/cli_overrides.yml index 15ff610dae..a4e883b7a5 100644 --- a/.github/workflows/cli_overrides.yml +++ b/.github/workflows/cli_overrides.yml @@ -105,7 +105,10 @@ jobs: continue-on-error: true working-directory: orca-test-repo run: | - python -m pytest test_cli_overrides.py -c pytest.ini -v --effect-full \ + # -rA prints the per-stage summaries: pytest captures stdout on + # passing tests, so without it every "grep override sweep" below + # finds nothing and the job summary says "no stage summaries" + python -m pytest test_cli_overrides.py -c pytest.ini -v -rA --effect-full \ --effect-shard ${{ matrix.shard }}/8 \ --orca-bin "$ORCA_BIN" --orca-source "$ORCA_SOURCE" \ 2>&1 | tee ../sweep.log