Docker release - pin buildkit to v0.19.0#148372
Closed
atalman wants to merge 7 commits intopytorch:mainfrom
Closed
Docker release - pin buildkit to v0.19.0#148372atalman wants to merge 7 commits intopytorch:mainfrom
atalman wants to merge 7 commits intopytorch:mainfrom
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/148372
Note: Links to docs will display an error until the docs builds have been completed. ❌ 2 New Failures, 46 PendingAs of commit f052b12 with merge base a414138 ( NEW FAILURES - The following jobs have failed:
UNSTABLE - The following job is marked as unstable, possibly due to flakiness on trunk:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
seemethere
approved these changes
Mar 3, 2025
Contributor
Author
|
@pytorchmergebot merge -f "lint and docker builds are clear" |
Collaborator
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 |
pytorchmergebot
pushed a commit
to min-jean-cho/pytorch
that referenced
this pull request
Mar 5, 2025
Fix nightly build failure during arm64 docker build (since 02.21.2025): https://github.com/pytorch/pytorch/actions/runs/13452177170/job/37588508155#step:12:851 Error: ``` pytorch#10 73.62 Segmentation fault (core dumped) pytorch#10 73.67 qemu: uncaught target signal 11 (Segmentation fault) - core dumped pytorch#10 73.85 Segmentation fault (core dumped) pytorch#10 73.85 dpkg: error processing package libc-bin (--configure): pytorch#10 73.85 installed libc-bin package post-installation script subprocess returned error exit status 139 ``` Looks like we are hitting: moby/buildkit#5783 Update setup-qemu and buildkit actions to v3 and buildkit to v0.19.0 Please note: CUDA 12.8 error is not related to this failure in nightly cpu arm64. Looks like we are trying to install release torch when running on PR. Cuda 12.8 build is not released yet, hence a failure. Will send followup to make sure we are using nightly torch when running on PR. Pull Request resolved: pytorch#148372 Approved by: https://github.com/seemethere
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
3 participants
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.
Fix nightly build failure during arm64 docker build (since 02.21.2025): https://github.com/pytorch/pytorch/actions/runs/13452177170/job/37588508155#step:12:851
Error:
Looks like we are hitting: moby/buildkit#5783
Update setup-qemu and buildkit actions to v3 and buildkit to v0.19.0
Please note: CUDA 12.8 error is not related to this failure in nightly cpu arm64. Looks like we are trying to install release torch when running on PR. Cuda 12.8 build is not released yet, hence a failure. Will send followup to make sure we are using nightly torch when running on PR.