Add missing pytorch-linux-jammy-py3.12-triton-cpu Docker image#140571
Add missing pytorch-linux-jammy-py3.12-triton-cpu Docker image#140571huydhn wants to merge 1 commit intopytorch:mainfrom
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/140571
Note: Links to docs will display an error until the docs builds have been completed. ❗ 1 Active SEVsThere are 1 currently active SEVs. If your PR is affected, please view them below: ❌ 1 New FailureAs of commit 2940167 with merge base 03cccaa ( NEW FAILURE - The following job has failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
|
@pytorchbot merge -f 'Should be ok now as all docker build and lint jobs have passed' |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
|
@pytorchbot revert -m 'Not sure why lint fails, maybe a landrace' -c weird I will rebase and reland this |
|
@pytorchbot successfully started a revert job. Check the current status here. |
#140571)" This reverts commit 51e0996. Reverted #140571 on behalf of https://github.com/huydhn due to Not sure why lint fails, maybe a landrace ([comment](#140571 (comment)))
|
@huydhn your PR has been successfully reverted. |
|
@pytorchbot drci |
|
@pytorchbot merge -f 'ONNX failure is real but not related to this PR, merging this to fix the rate limit issue first and I will do a forward fix after then' |
Merge startedYour change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
…ch#140571) When investigating the burst of 429 rate limit failures from docker.io yesterday, I found out that ` pytorch-linux-jammy-py3.12-triton-cpu` hasn't been added to docker build workflow at all. The bad effect is that the image is rebuilt on every job https://github.com/pytorch/pytorch/actions/runs/11808772774/job/32900628381 Pull Request resolved: pytorch#140571 Approved by: https://github.com/seemethere, https://github.com/wdvr
pytorch#140571)" This reverts commit 51e0996. Reverted pytorch#140571 on behalf of https://github.com/huydhn due to Not sure why lint fails, maybe a landrace ([comment](pytorch#140571 (comment)))
…ch#140571) When investigating the burst of 429 rate limit failures from docker.io yesterday, I found out that ` pytorch-linux-jammy-py3.12-triton-cpu` hasn't been added to docker build workflow at all. The bad effect is that the image is rebuilt on every job https://github.com/pytorch/pytorch/actions/runs/11808772774/job/32900628381 Pull Request resolved: pytorch#140571 Approved by: https://github.com/seemethere, https://github.com/wdvr
When investigating the burst of 429 rate limit failures from docker.io yesterday, I found out that
pytorch-linux-jammy-py3.12-triton-cpuhasn't been added to docker build workflow at all. The bad effect is that the image is rebuilt on every job https://github.com/pytorch/pytorch/actions/runs/11808772774/job/32900628381