summaryrefslogtreecommitdiff
path: root/buildstream/element.py
diff options
context:
space:
mode:
authorSam Thursfield <sam.thursfield@codethink.co.uk>2018-02-22 12:02:44 +0000
committerSam Thursfield <sam.thursfield@codethink.co.uk>2018-02-22 12:02:44 +0000
commitb2197bc2aa7300ec9663686ce767aa02d78bbb99 (patch)
tree76cde6640729345e1eeb5c0ce3991b8b2ac2d265 /buildstream/element.py
parent3d94bd25ddb74ab05a4c9f4785c7f3d8441df23f (diff)
downloadbuildstream-b2197bc2aa7300ec9663686ce767aa02d78bbb99.tar.gz
_ostree.py: Disable OSTree's minimum disk space check in our repossam/disable-ostree-free-space-check
This interacts badly with our builds, usually if the check does fire it's at the point that we are trying to commit a completed build (which may have taken a long time to complete) into the cache. Even though there might be enough space available to store the build, the error causes BuildStream to consider it "failed" and forces the user to start again. This aims to fix https://gitlab.com/BuildStream/buildstream/issues/216 although there is some evidence that it does not completely do so. BuildStream currently has no minimum disk space check, and no way to automatically clean up the cache. There is an open issue for this: https://gitlab.com/BuildStream/buildstream/issues/135
Diffstat (limited to 'buildstream/element.py')
0 files changed, 0 insertions, 0 deletions