GEODE-8347: use same benchmarks branch as geode branch #5361
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
…the way we release also balance max_in_flight according to how long each job takes
dickcav
approved these changes
Jul 9, 2020
smgoller
approved these changes
Jul 9, 2020
onichols-pivotal
deleted the
GEODE-8347-use-same-benchmarks-branch-as-geode-branch
branch
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.
Geode 1.12 release included geode-benchmarks from support/1.12, but the pipeline definition is still using benchmarks from develop, as is 1.13. Fix to use matching branch names between geode and geode-examples. Also rebalance max_in_flight based on how long each benchmark job takes.