Run runtime benchmarks after each merge #1662
Merged
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
Kobzol
force-pushed
the
runtime-bench-next
branch
from
a0393c9 to
2a674ad
Compare
Kobzol
force-pushed
the
runtime-bench-next
branch
from
2a674ad to
3d1e8c6
Compare
Mark-Simulacrum
approved these changes
Jul 27, 2023
Member
Author
|
Okay, here goes nothing :) |
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.
This PR finishes the MVP of runtime benchmarks 🎉 After it, runtime benchmarks should be executed together with compile benchmarks for each merge or try build.
Blocked on:
#1626,#1650,#1651Closes: #69 (it took 7 years, but the issue does say "Low priority", so...)