Repository navigation
perf-benchcomp CI fails when pushing a new release #2744
Description
Activity
The root cause of the problem is that
github.event.beforeisn't set for new branches, and likely the same is true for tags. The fix should likely be that we removetags: - kani-*from
.github/workflows/bench.yml. We still have the performance comparison on the merge intomainanyway.Reacted by Adrian Palacios
Proposed change: Do not run the
perf-benchcompwhen pushing a release tag.Motivation:
perf-benchcompjobs get triggered after pushing a release tag and they fail with some error that I don't understand. It doesn't make sense to runperf-benchcompin CI anyway because the candidate commit will have already done it.I was surprised to find that the CI job failed when doing the 0.36.0 release (job here). Then I check what happened during the 0.35.0 release and saw the same here (job here).