We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracker for upstream issue: docker/build-push-action#1309
At the time of writing this issue, this has been failing for the past 3 days: https://github.com/ggml-org/llama.cpp/actions/workflows/docker.yml
It was fixed in #11472 but now the problem came back.
CC @ggerganov @slaren for visibility
The text was updated successfully, but these errors were encountered:
I noticed that and these failures are actually now caused by a different issue:
https://github.com/ggml-org/llama.cpp/actions/runs/13322407195/job/37209322813#step:8:2252
#11 128.3 Processing triggers for libc-bin (2.35-0ubuntu3.8) ... #11 128.4 qemu: uncaught target signal 11 (Segmentation fault) - core dumped #11 128.9 Segmentation fault (core dumped) #11 129.0 qemu: uncaught target signal 11 (Segmentation fault) - core dumped #11 129.7 Segmentation fault (core dumped) #11 129.7 dpkg: error processing package libc-bin (--configure): #11 129.7 installed libc-bin package post-installation script subprocess returned error exit status 139
Googling a bit:
tonistiigi/binfmt#240
Edit: nvm, it might be the same issue
Sorry, something went wrong.
I'm running a CI with tonistiigi/binfmt:qemu-v7.0.0-28 on my fork: https://github.com/ngxson/llama.cpp/actions/runs/13346220830/job/37276975481
tonistiigi/binfmt:qemu-v7.0.0-28
Will make a PR if it fixes the issue
No branches or pull requests
Tracker for upstream issue: docker/build-push-action#1309
At the time of writing this issue, this has been failing for the past 3 days: https://github.com/ggml-org/llama.cpp/actions/workflows/docker.yml
It was fixed in #11472 but now the problem came back.
CC @ggerganov @slaren for visibility
The text was updated successfully, but these errors were encountered: