From 25dedb857d7de4937555683acd623a62ea039cb3 Mon Sep 17 00:00:00 2001 From: 4gray Date: Tue, 6 Oct 2026 10:37:56 +0200 Subject: [PATCH] ci(perf): check the journey counters whenever a summary was written Review follow-up (Greptile): the check ran only after the composite action succeeded, so a failed job-summary report after a written summary.json skipped every baseline. It now runs unless the job was cancelled, as long as the action produced a summary path. Co-Authored-By: Claude Opus 5.5 --- .github/workflows/ci.yml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml index 679dea1cb..08f56981e 100644 --- a/.github/workflows/ci.yml +++ b/.github/workflows/ci.yml @@ -333,8 +333,11 @@ jobs: # docs/architecture/performance-journeys.md). Here and not in the # composite action, so the weekly tightening still measures a run # that would fail it. tools/performance tests keep this list equal - # to the journey entries of journey-baselines.json. + # to the journey entries of journey-baselines.json. It also runs + # when a later step of the action (the job-summary report) failed + # after the summary was written, so the counters are still checked. - name: Check the journey counters against the baselines + if: ${{ !cancelled() && steps.journeys.outputs.summary != '' }} env: SUMMARY: ${{ steps.journeys.outputs.summary }} run: >-