Configure performance benchmarks #2810
Draft
Conversation
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
LZRS
force-pushed
the
perf-benchmark-scripts
branch
2 times, most recently
from
ed45185 to
079953b
Compare
LZRS
force-pushed
the
perf-benchmark-scripts
branch
5 times, most recently
from
6a614e3 to
f04d16b
Compare
LZRS
force-pushed
the
perf-benchmark-scripts
branch
from
f04d16b to
5c55648
Compare
also migrated ksp and room to versions supporting k2
LZRS
force-pushed
the
perf-benchmark-scripts
branch
2 times, most recently
from
42e393c to
979ac86
Compare
LZRS
force-pushed
the
perf-benchmark-scripts
branch
2 times, most recently
from
b0da7dc to
e4ce7eb
Compare
LZRS
force-pushed
the
perf-benchmark-scripts
branch
from
e4ce7eb to
874090e
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.
IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).
Fixes #2791
Resolves #2811
Description
Clear and concise code change description.
Alternative(s) considered
Have you considered any alternatives? And if so, why have you chosen the approach in this PR?
Type
Choose one: (Bug fix | Feature | Documentation | Testing | Code health | Builds | Releases | Other)
Screenshots (if applicable)
Checklist
./gradlew spotlessApplyand./gradlew spotlessCheckto check my code follows the style guide of this project../gradlew checkand./gradlew connectedCheckto test my changes locally.