update version cap to 2.7 of pytorch and pytorch-lightning #5000
Conversation
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
|
multimodal tests failing appear to be same cause as the master branch failures. |
… 2.6 change of default from False to True
… 2.6 change of default from False to True
|
Job PR-5000-0e710b1 is done. |
|
@FireballDWF Thanks for the contrib!! @tonyhoo Looks like CI has passed, if all looks good to you, feel free to approve and merge. Cheers! |
tonyhoo
approved these changes
Apr 7, 2025
This was referenced Apr 8, 2025
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.
update version cap to 2.7 of pytorch and pytorch-lightning, as well as increasing cap of torchvision.
Not only will this allow direct users of autogluon to start using pytorch 2.6, it will also allow users of downstream projects like Sagemaker Distribution to use pytorch 2.6 once autogluon cuts a release
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.