Run benchmarks in "test" mode, in CI - #20114
Merged
Merged
Conversation
huonw
changed the title
huonw
marked this pull request as ready for review
October 29, 2023 05:28
This reverts commit 47a8bb6.
stuhood
enabled auto-merge (squash)
October 31, 2023 18:58
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Cargo/criterion supports running benchmarks in "test" mode, where they only execute once and don't actually benchmark, but at least validate that the code seems to run. This fixes #20067 by switching CI to do this.
The store benchmark (the only benchmarks at the moment) seems to take ~80s to run in CI. Is it worth it to avoid problems like #20057?