Files
releases/build/gobenchdata-checks.yml
T
Stephan Renatus dc77f2e259 workflows: report benchmark regressions back to pull request
Let's see if this works, it's a bit experimental at this point.

The twist comparred to how it's been done in EOPA (for example) is that
we're running the benchmarks post-merge, and report back if at the end
we find a failing check. This way, the PR goes green without having to
wait for the benchmarks, but there's still a connection between PR and
benchmark.

Signed-off-by: Stephan Renatus <stephan.renatus@gmail.com>
2026-05-08 10:01:50 +02:00

9 lines
228 B
YAML

checks:
- name: ns-per-op regression
description: Flag if NsPerOp regresses by more than 10%
package: ""
benchmarks: []
diff: (current.NsPerOp - base.NsPerOp) / base.NsPerOp * 100
thresholds:
max: 10