-
Notifications
You must be signed in to change notification settings - Fork 9.1k
New issue
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
ci : fix Docker workflow #3628
Comments
It's just that the disk is full, right? Or maybe just isn't allocated large enough to run the current tasks. (At least all the ones I saw were just |
This might be relevant: docker/build-push-action#968. |
I thought I'd give this a shot, but couldn't manage to replicate the issue. after forking, the "Publish Docker image" workflow runs fine in my repo. I tried reverting back to 11bff29 since that was the commit of the most recent failure before the workflow was manually disabled, but even that succeeded 🤷 I went ahead and added the pr #4150 |
@ggerganov thoughts on that PR? |
Should I try to merge #4150 and re-enable the docker action? |
Yea let's try it |
nice looks like it's worked! |
On another note I see there is |
#4584 here's my attempt at this |
looks ok in my fork: https://github.com/samm81/llama.cpp/actions/runs/7304004733 |
Not sure, will have to disable it again because my notifications are being spammed with Docker failures. Hopefully we can figure out the issue eventually |
Just saw #4603 - let's see if this resolves it |
it looks like the problems in this issue have both been solved - seems there's some intermittent issue with the |
I just disabled the workflow since it has been crashing for a while now:
The text was updated successfully, but these errors were encountered: