Repository navigation
[ci] Fix CI - #1512
Merged
Merged
[ci] Fix CI#1512
Conversation
meta-cla
Bot
added
the
CLA Signed
aelavender
marked this pull request as ready for review
November 13, 2025 21:53
aelavender
requested review from
divyanshk,
psaikaushik,
ramanishsingh and
scotts
November 13, 2025 21:54
|
@aelavender has imported this pull request. If you are a Meta employee, you can view this in D87016927. |
|
Will there be a separate pull request adding Python 3.14 support? |
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
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.
Most CI has not been running in this repo. This PR re-enables it.
if github.repository == 'pytorch/data'. Since we moved tometa-pytorch, these checks have failed and jobs are skipped. Update to point at the correct repo.torch. This is becausetorchtrunk no longer supports py3.9 and they have stopped building nightlies for it. Update to remove p3.9 from our matrix.The failed job
Run Nodes Tests / test (windows-latest, 3.11)is a legit test failure. This test appears to rely on some timeouts, so might be flaky.As of this writing, still waiting on StatefulDataLoader tests to complete (these take a long time), but they are at least kicked off correctly, which is an improvement over them being skipped.
Note: currently we do NOT have CI running against python 3.14 or 3.14t. We should probably add this.