-
Notifications
You must be signed in to change notification settings - Fork 204
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
Add "early-abort" in asset/results cleanup jobs based on df-output #3750
Conversation
7303bf9
to
309135a
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.
I see that you add asset/results cleanup in the same step. Can we try to focus on one at a time, e.g. results only first?
If it really has to be I can split the commit retrospectively (which likely means rebasing and solving conflicts of the 2nd commit later). However, I don't think it is necessary because the behavior can still be configured individually. |
Sure. Whatever works best for you. Just wanted to suggest a way to get independent parts completed quicker, including deployment, risk in production, potential reverts, etc. |
2917ff2
to
35edeb5
Compare
Codecov Report
@@ Coverage Diff @@
## master #3750 +/- ##
==========================================
+ Coverage 96.42% 96.47% +0.04%
==========================================
Files 367 368 +1
Lines 32321 32374 +53
==========================================
+ Hits 31167 31233 +66
+ Misses 1154 1141 -13
Continue to review full report at Codecov.
|
* Make the minimum used disk space configurable having the new behavior not enabled by default * See https://progress.opensuse.org/issues/88121#note-10
35edeb5
to
aefbbd2
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
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.
Awesome test, easy to read :)
* That would give us the space between 80 % and 90 % usage as "buffer" between cleanup and the disk space alert * Not effective until os-autoinst/openQA#3750 is deployed * See https://progress.opensuse.org/issues/88121
enabled by default