Closed hassila closed 10 months ago
All modified and coverable lines are covered by tests :white_check_mark:
Comparison is base (
02b4da9
) 67.18% compared to head (1db45b5
) 66.84%.
Pull request had an unknown failure Pull request benchmark comparison [ubuntu-latest] with 'main' run at 2024-01-11T11:52:23+00:00
Description
For benchmarks that are not completely stable (in e.g. syscall/malloc count) due to use of e.g. async or networking, it is desirable to also be able to specify some leeway for benchmarks even for the absolute checks from thresholds.
This fixes https://github.com/ordo-one/package-benchmark/issues/220
By default the behaviour for absolute thresholds checks are as previously (strict, zero improvements/regressions are allowed), but now it is possible to define both absolute and relative thresholds for the benchmarks (as documented at https://swiftpackageindex.com/ordo-one/package-benchmark/1.21.3/documentation/benchmark/writingbenchmarks)
How Has This Been Tested?
Manual testing.
Minimal checklist:
DocC
code-level documentation for any public interfaces exported by the package