Skip to content
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
merged 35 commits into from Mar 8, 2024

Conversation

countvajhula
Copy link
Collaborator

@countvajhula countvajhula commented Jan 12, 2024

Summary of Changes

We could use this to gather the new benchmark data using GitHub's CI infrastructure.

Things we would need to do:

  1. Publish the new benchmarks suite as a package on the Racket Package Index (takes about 10-15 minutes to appear, once published)
  2. Address the "TODO"s in the new workflow file.

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

  • In contributing, I relinquish any copyright claims on my contribution and freely release it into the public domain in the simple hope that it will provide value. (Why)

@countvajhula countvajhula changed the base branch from lets-write-a-qi-compiler to main January 16, 2024 23:29
@countvajhula
Copy link
Collaborator Author

This PR has a lot of noisy commits for testing, so squash-merging this one. Changes were OK'd in today's meeting.

@countvajhula countvajhula merged commit de6d6b4 into drym-org:main Mar 8, 2024
11 checks passed
@countvajhula
Copy link
Collaborator Author

🤦 I meant to squash merge... but I didn't 😭 😭 😭

@benknoble
Copy link
Collaborator

Woops! When I saw the force-push, I was hoping you'd rebased and dropped the noise commits :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants