Am 27.10.2015 um 17:35 schrieb Adrian Schröter:
On Dienstag, 27. Oktober 2015, 17:32:57 CET wrote Olaf Hering:
The buildlog of a package which failed due to ENOSPC has no info how much diskspace was actually available. This makes it cumbersome to create a _constraints file. How much diskspace has a VM?
there are different ones ... and we don't have an interface to request this information yet.
A simple "df -h /" (or whatever) after the "swapon -v" would be a start.
However, it is actually more interessting how much space is needed by the job. If you still have a successfull job from this build you can check the used resources via the _statistics file.
There is no successful build for TW, but for 13.?. From these logs it looks like 5G instead of 4G might work for this pkg. Olaf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org