From 75b402638786e38436b3d410697b0b725514675e Mon Sep 17 00:00:00 2001 From: William Woodruff Date: Tue, 13 Feb 2024 17:18:07 -0500 Subject: [PATCH] Drop cache-hit check The logic here is faulty: there will be some cache hits for results that *did* have regressions. So we need to be more precise here. Signed-off-by: William Woodruff --- .github/workflows/regression.yml | 3 --- 1 file changed, 3 deletions(-) diff --git a/.github/workflows/regression.yml b/.github/workflows/regression.yml index 2372bd3f..b2b15851 100644 --- a/.github/workflows/regression.yml +++ b/.github/workflows/regression.yml @@ -24,9 +24,6 @@ jobs: id: run-harnesses - name: run regression checks - # A cache hit means that neither limbo.json nor any of the harnesses - # have changed, so there's no value in checking for regressions. - if: steps.run-harnesses.outputs.cache-hit != 'true' run: make run ARGS="regression" env: GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}"