ci: don't run benchmark in debug mode #1566
Merged
Conversation
This file contains 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
wjones127
requested review from
houqp,
xianwill,
fvaleye,
roeap,
rtyler and
mosyp
as code owners
rtyler
approved these changes
Jul 27, 2023
wjones127
force-pushed
the
ci/no-benchmark-tests
branch
from
944bc98 to
5ccd190
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I realized our Python CI is very slow because we are running the benchmarks in debug mode. We already have a separate CI job that runs them in release mode (which is actually useful), so just disabling it in the main job.