-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gather new benchmark data #150
Merged
countvajhula
merged 35 commits into
drym-org:main
from
countvajhula:gather-new-benchmark-data
Mar 8, 2024
Merged
Gather new benchmark data #150
countvajhula
merged 35 commits into
drym-org:main
from
countvajhula:gather-new-benchmark-data
Mar 8, 2024
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
countvajhula
had a problem deploying
to
test-env
January 12, 2024 01:45 — with
GitHub Actions
Failure
countvajhula
force-pushed
the
gather-new-benchmark-data
branch
from
January 16, 2024 23:30
dd2e9a7
to
d754695
Compare
countvajhula
had a problem deploying
to
test-env
January 16, 2024 23:32 — with
GitHub Actions
Failure
countvajhula
had a problem deploying
to
test-env
January 19, 2024 02:02 — with
GitHub Actions
Failure
countvajhula
had a problem deploying
to
test-env
January 19, 2024 02:10 — with
GitHub Actions
Failure
countvajhula
had a problem deploying
to
test-env
January 19, 2024 02:27 — with
GitHub Actions
Failure
countvajhula
had a problem deploying
to
test-env
January 19, 2024 02:57 — with
GitHub Actions
Failure
countvajhula
had a problem deploying
to
test-env
January 19, 2024 03:01 — with
GitHub Actions
Failure
countvajhula
had a problem deploying
to
test-env
January 19, 2024 03:12 — with
GitHub Actions
Failure
countvajhula
had a problem deploying
to
test-env
January 20, 2024 00:43 — with
GitHub Actions
Failure
countvajhula
force-pushed
the
gather-new-benchmark-data
branch
from
March 1, 2024 23:47
6c46db6
to
e703041
Compare
This PR has a lot of noisy commits for testing, so squash-merging this one. Changes were OK'd in today's meeting. |
🤦 I meant to squash merge... but I didn't 😭 😭 😭 |
Woops! When I saw the force-push, I was hoping you'd rebased and |
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.
Summary of Changes
We could use this to gather the new benchmark data using GitHub's CI infrastructure.
Things we would need to do:
It should then publish the new benchmarks on GitHub Pages at
<root URL>/qi/competitive-benchmarks
Another possibility is we could have the
make new-benchmarks
target only generate text output data to STDOUT. Then we could manually copy it in the job UI, and feed it into the charts manually.Public Domain Dedication