Skip to content

[submodule] upgrade cutlass version to 4.2.1 and completely resolved python/cutlass name collision#164156

Closed
henrylhtsang wants to merge 1 commit intopytorch:mainfrom
henrylhtsang:export-D83489362
Closed

[submodule] upgrade cutlass version to 4.2.1 and completely resolved python/cutlass name collision#164156
henrylhtsang wants to merge 1 commit intopytorch:mainfrom
henrylhtsang:export-D83489362

Conversation

@henrylhtsang
Copy link
Contributor

@henrylhtsang henrylhtsang commented Sep 29, 2025

@pytorch-bot
Copy link

pytorch-bot bot commented Sep 29, 2025

🔗 Helpful Links

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

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

✅ No Failures

As of commit dd74531 with merge base 8f32adc (image):
💚 Looks good so far! There are no failures yet. 💚

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

@facebook-github-bot
Copy link
Contributor

@henrylhtsang has exported this pull request. If you are a Meta employee, you can view the originating diff in D83489362.

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Sep 29, 2025
@Skylion007
Copy link
Collaborator

Apply the lint changes and it looks good to merge

…python/cutlass name collision (pytorch#164156)

Summary: Pull Request resolved: pytorch#164156

Differential Revision: D83489362
@facebook-github-bot
Copy link
Contributor

@henrylhtsang has exported this pull request. If you are a Meta employee, you can view the originating diff in D83489362.

@henrylhtsang
Copy link
Contributor Author

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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

@pytorchmergebot
Copy link
Collaborator

The merge job was canceled or timed out. This most often happen if two merge requests were issued for the same PR, or if merge job was waiting for more than 6 hours for tests to finish. In later case, please do not hesitate to reissue the merge command
For more information see pytorch-bot wiki.

@Skylion007
Copy link
Collaborator

@pytorchbot merge

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

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

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