Skip to content

Conversation

@malfet
Copy link
Contributor

@malfet malfet commented Oct 1, 2025

To allow viable/strict to move forward, after #164260 was landed

To allow viable/strict to move forward, after #164260 was landed
@malfet malfet requested a review from a team as a code owner October 1, 2025 18:00
@pytorch-bot pytorch-bot bot added the topic: not user facing topic category label Oct 1, 2025
@pytorch-bot
Copy link

pytorch-bot bot commented Oct 1, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/164374

Note: Links to docs will display an error until the docs builds have been completed.

⏳ No Failures, 13 Pending

As of commit 04f66cf with merge base ebd0707 (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@seemethere
Copy link
Member

@pytorchbot merge -f 'needed for viable/strict upgrade'

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

Chao1Han pushed a commit to Chao1Han/pytorch that referenced this pull request Oct 21, 2025
To allow viable/strict to move forward, after pytorch#164260 was landed

Pull Request resolved: pytorch#164374
Approved by: https://github.com/seemethere
@github-actions github-actions bot deleted the malfet-patch-6 branch November 1, 2025 02:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants