Skip to content

Add upper bounds to lock_pytorch_cpu torch versions #11033

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jan 28, 2025
Merged

Add upper bounds to lock_pytorch_cpu torch versions #11033

merged 1 commit into from
Jan 28, 2025

Conversation

zanieb
Copy link
Member

@zanieb zanieb commented Jan 28, 2025 •
edited
Loading

Presumably this is a better alternative to #11031

@zanieb zanieb added the testing Internal testing of behavior label Jan 28, 2025
@zanieb zanieb mentioned this pull request Jan 28, 2025
Closed
@zanieb zanieb enabled auto-merge (squash) January 28, 2025 18:45
BurntSushi
BurntSushi approved these changes Jan 28, 2025
View reviewed changes
Copy link
Member

@BurntSushi BurntSushi left a comment

Choose a reason for hiding this comment

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

Makes sense to me. Interesting that it looks like some markers got merged?

@zanieb zanieb merged commit 7949672 into main Jan 28, 2025
73 checks passed
@zanieb zanieb deleted the zb/torch-again-again branch January 28, 2025 18:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@BurntSushi BurntSushi BurntSushi approved these changes

Assignees
No one assigned
Labels
testing Internal testing of behavior
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@zanieb @BurntSushi