Update to Python Project Template v1.4.5; Integrate with ASV Benchmarking #340
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #340 +/- ##
=======================================
Coverage 94.66% 94.66%
=======================================
Files 24 24
Lines 1556 1556
=======================================
Hits 1473 1473
Misses 83 83 ☔ View full report in Codecov by Sentry. |
dougbrn
changed the title
drewoldag
reviewed
Jan 2, 2024
drewoldag
reviewed
Jan 2, 2024
drewoldag
approved these changes
Jan 2, 2024
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.
The vast majority of lines added/removed here are from the copier update command (grabbing the latest and greatest from ppt 1.4.5). This PR adds a few starter benchmarks for TAPE ASV integration. The github-actions comment below demonstrates that the PR comparison workflow is working as expected.
However, I don't think there's a way to test the gh-pages deployment until this gets merged into main, based on that I would like to try to merge this with a minimal benchmarking suite, verify whether the page deployment works as expected, and then build out the benchmarking suite in a later PR.