-
Notifications
You must be signed in to change notification settings - Fork 55
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
builder-common: Run additional prune job to free up space #1031
Conversation
Hmm, why not reprovision the builder with a larger disk size first? That seems like something we should do anyway, and would likely drop the need for this. |
I recall a conversation in which it was suggested that 200GB should suffice. I'm more than happy to drop this and open another PR if that is debunked |
i think we can do both. |
The Aarch64 builder consistently complains about a lack of space, particularly around 10am UTC / 12pm BST (London). This additional prune job aims to mitigate the space issues. See: openshift/os#1554
ecbeb8b
to
b7b0118
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
The Aarch64 builder consistently complains about a lack of space. After a brief discussion we decided to increase its size. See: openshift/os#1554 Ref: coreos#1031 (comment)
The Aarch64 builder consistently complains about a lack of space. After a brief discussion we decided to increase its size. See: openshift/os#1554 Ref: #1031 (comment)
Suggestion implemented. Thank you!
The Aarch64 builder consistently complains about a lack of space, particularly around 10am UTC / 12pm BST (London).
This additional prune job aims to mitigate the space issues.
See: openshift/os#1554