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 <[email protected]>
C2SP · Feb 13, 2024 · 75b4026 · 75b4026
1 parent 345db64
commit 75b4026
Showing 1 changed file with 0 additions and 3 deletions.
diff --git 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 }}"