Get CI working with new black, torch, pytest #3318
Merged
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
fritzo
changed the title
|
Phew, looks like this is now ready to merge 😅 |
ordabayevy
approved these changes
Feb 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.
Blocking #3317
This PR performs a number of maintenance tasks to get our CI working again.
blackand reformat, completely automated. I haven't bumped black's version pin.torch.distributions.InverseGammaif available.This was breaking our docs build.
I've marked our old
InverseGammafor deprecation.test_benchmark.pyas stage=benchmark to avoid a new pytest warning.test_welford.pyand the CEVAE's prewhitener to avoid a new.var()warning in torch.