-
Notifications
You must be signed in to change notification settings - Fork 164
Free disk space before docker save in coq-docker workflow #2223
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
Conversation
|
@copilot Do not delete anything in Also what about seeing if you have permissions to write to /dev/sdb1 ? |
Updated in 8f1b127:
Total space freed: ~2GB from system-level caches without touching build artifacts. |
8f1b127 to
7227edb
Compare
7227edb to
75c1128
Compare
Co-authored-by: JasonGross <396076+JasonGross@users.noreply.github.com>
…dback Co-authored-by: JasonGross <396076+JasonGross@users.noreply.github.com>
Comment out the removal of actions-runner cached files in the workflow.
9ba4223 to
dee78b5
Compare
The
docker savestep was failing with "no space left on device" when disk usage reached 91% (6.7GB available of 72GB total). System-level caches were accumulating before the save operation.Changes
Added cleanup steps to remove system-level caches and uploaded artifacts:
fiat-crypto-build.tar.gzfrom working directory/home/runner/.rustup(~600MB) and/home/runner/actions-runner/cached(~1.4GB)Added enhanced diagnostics:
/dev/sdb1mount status and write permissionsdf -hbefore and after cleanupTotal space freed: ~2GB from system-level caches. Build artifacts in the working directory are preserved for use by subsequent jobs.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.