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

Update benchmark crates and workflow #3027

Merged
merged 10 commits into from Dec 11, 2022

Conversation

WorldSEnder
Copy link
Member

@WorldSEnder WorldSEnder commented Dec 10, 2022

Description

Updates the benchmark setup to the latest js-framework-benchmark setup.
Also separates the posting of comments and the update to the gh-pages branch to run the benchmarking with less priviledges.

When reviewing, pay most attention to .github/workflows/post-benchmark.yml as that workflow is not run as part of the PR (on purpose as it has elevated privileges).

Checklist

  • I have reviewed my own code
  • I have added tests

github-actions[bot]
github-actions bot previously approved these changes Dec 10, 2022
github-actions[bot]
github-actions bot previously approved these changes Dec 10, 2022
github-actions[bot]
github-actions bot previously approved these changes Dec 10, 2022
github-actions[bot]
github-actions bot previously approved these changes Dec 10, 2022
github-actions[bot]
github-actions bot previously approved these changes Dec 10, 2022
github-actions[bot]
github-actions bot previously approved these changes Dec 10, 2022
this doesn't comment on PR directly, still
benchmark-action/github-action-benchmark has open issues about it
github-actions[bot]
github-actions bot previously approved these changes Dec 10, 2022
Copy link
Member

@hamza1311 hamza1311 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

Can we delete the previous data? I don't think we should keep too much data around because of differences between GitHub provided runners. Also, our previous data wasn't really accurate either

@WorldSEnder
Copy link
Member Author

Can we delete the previous data? I don't think we should keep too much data around because of differences between GitHub provided runners. Also, our previous data wasn't really accurate either

I think we have to delete the data from the gh-pages branch. I'll merge this when I have time for follow-ups in case something breaks with the other action.

@WorldSEnder WorldSEnder merged commit 698bd56 into yewstack:master Dec 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants