Run benchmark against develop branch during PR #1321
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
zinc-benchmark
result varies greatly between different CI runs. Therefore, to identify how a PR affects zinc performance, cannot simply readzinc-benchmark
CI results from latest develop commit and PR commit to cross-compare two results.Changes
We can run
zinc-benchmark
against develop branch in the same CI run. This way, both results are from the same machine, hence can be cross-compared.Validating the PR
The CI for this PR shows the following two benchmark results
The two runs have very similar number, as desired.