Advance the torch floor to 2.14 - #8
Closed
github-actions[bot] wants to merge 1 commit into
Closed
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Opened by the dependency watch (plans repo: plans/torch_port/active/python_matrix_nightly_check.md).
Trigger: torch 2.14.0 publishes CPU-index Linux x86_64 wheels for Python 3.10, 3.11, 3.12, 3.13, 3.14 and 3.15.
Policy: mbirtorch tests the Python versions torch supports, and advances its torch floor deliberately.
Branch cut from
26bd0ea988bd83e99e8e4cbe2fa8223ac4d104d2.The torch floor advance's green checks cover the CPU suite; the Triton and CUDA paths are proven by the cluster nightly after the merge.