[CD] Update triton xpu release branch naming convention#177723
[CD] Update triton xpu release branch naming convention#177723chuanqi129 wants to merge 1 commit into
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/177723
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 1b58095 with merge base 8e7898a ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
087e952 to
4a75cc0
Compare
4a75cc0 to
752319f
Compare
752319f to
1b58095
Compare
|
@pytorchbot merge |
Merge startedYour 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 |
|
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 |
|
@pytorchbot merge |
Merge startedYour 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 |
As the triton xpu has standalone repo, and the update cadence in pytorch is different with upstream triton. To mitigate the version gap between those 2 kinds of triton, consider patch version into release branch naming for triton xpu. It just impact release wheel build. Pull Request resolved: #177723 Approved by: https://github.com/EikanWang, https://github.com/atalman Co-authored-by: Xia-Weiwen <12522207+Xia-Weiwen@users.noreply.github.com>
As the triton xpu has standalone repo, and the update cadence in pytorch is different with upstream triton. To mitigate the version gap between those 2 kinds of triton, consider patch version into release branch naming for triton xpu. It just impact release wheel build. Pull Request resolved: pytorch#177723 Approved by: https://github.com/EikanWang, https://github.com/atalman
As the triton xpu has standalone repo, and the update cadence in pytorch is different with upstream triton. To mitigate the version gap between those 2 kinds of triton, consider patch version into release branch naming for triton xpu. It just impact release wheel build. Pull Request resolved: pytorch#177723 Approved by: https://github.com/EikanWang, https://github.com/atalman
As the triton xpu has standalone repo, and the update cadence in pytorch is different with upstream triton. To mitigate the version gap between those 2 kinds of triton, consider patch version into release branch naming for triton xpu. It just impact release wheel build. Pull Request resolved: pytorch#177723 Approved by: https://github.com/EikanWang, https://github.com/atalman
As the triton xpu has standalone repo, and the update cadence in pytorch is different with upstream triton. To mitigate the version gap between those 2 kinds of triton, consider patch version into release branch naming for triton xpu. It just impact release wheel build.