Closed bantonsson closed 3 weeks ago
Benchmark execution time: 2024-10-10 20:34:12
Comparing candidate commit 687b3dc in PR branch ban/make-coverage-successs-optional
with baseline commit f363618 in branch main
.
Found 3 performance improvements and 0 performance regressions! Performance is the same for 48 metrics, 2 unstable metrics.
execution_time
[-16.831µs; -16.720µs] or [-3.466%; -3.443%]throughput
[+73433.244op/s; +73921.637op/s] or [+3.566%; +3.590%]execution_time
[-215.654ns; -206.778ns] or [-7.247%; -6.948%]Omitted due to size.
What does this PR do?
Allows merging of a PR even if Coverage fails
Motivation
Strange behavior with code coverage and library paths in CI leads to failures that are not related to the PRs.
Additional Notes
Anything else we should know when reviewing?
How to test the change?
Describe here in detail how the change can be validated.