Uh oh!
There was an error while loading. Please reload this page.
Follow-up PR to finish updating the performance regression workflow - #401
Merged
Merged
Conversation
nirosys
marked this pull request as ready for review
January 23, 2025 01:14
rmarrowstone
approved these changes
Jan 23, 2025
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
Sign up for freeto 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.
Issue #, if available: n/a
Description of changes:
The previous PR #379 updated half of the perf regression workflow to use the pyproject.toml for the PR-side of the benchmarking. This PR follows up to update the HEAD-side to use pyproject.toml now that the migration has been merged.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.