[opensuse-buildservice] buildlog lacks info about diskspace
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? The docs do not list default values: http://openbuildservice.org/help/manuals/obs-reference-guide/cha.obs.build_j... Olaf -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
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. 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. The webui is showing this here for example: https://build.opensuse.org/package/statistics/hardware:RC-Model/apm_planner?arch=x86_64&repository=openSUSE_13.1
The docs do not list default values: http://openbuildservice.org/help/manuals/obs-reference-guide/cha.obs.build_j...
Olaf
-- Adrian Schroeter email: adrian@suse.de SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
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
On Tuesday 27 October 2015 17:35:52 Adrian Schröter wrote:
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.
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.
The webui is showing this here for example:
https://build.opensuse.org/package/statistics/hardware:RC-Model/apm_planner ?arch=x86_64&repository=openSUSE_13.1
The docs do not list default values: http://openbuildservice.org/help/manuals/obs-reference-guide/cha.obs.build _job_constraints.html
Olaf
I just wanted to know the resources required for a larger number of packages and repos. Instead of clicking through the webui, a hacked an osc plugin to do it for me. $> osc prjresources Kernel:stable "standard,PPC,ARM" "ppc64,aarch64,x86_64" "kernel-debug,kernel-default,kernel-vanilla,kernel-xen,kernel-pv" --- Kernel:stable standard x86_64 --- kernel-debug: Disk: 15711 MByte Memory: 885 MByte Time: 10034 s kernel-default: Disk: 15675 MByte Memory: 1262 MByte Time: 6245 s kernel-vanilla: Disk: 16273 MByte Memory: 728 MByte Time: 20519 s kernel-xen: Disk: 14564 MByte Memory: 1277 MByte Time: 6617 s kernel-pv: Disk: 15815 MByte Memory: 764 MByte Time: 11427 s --- Kernel:stable PPC ppc64 --- kernel-debug: Disk: 14029 MByte Memory: 725 MByte Time: 7518 s kernel-default: Disk: 13998 MByte Memory: 783 MByte Time: 7351 s kernel-vanilla: Disk: 14667 MByte Memory: 1123 MByte Time: 6225 s --- Kernel:stable ARM aarch64 --- kernel-default: Disk: 13884 MByte Memory: 1098 MByte Time: 12511 s kernel-vanilla: Disk: 14530 MByte Memory: 748 MByte Time: 9972 s Kind regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019 work: +49 2405 49936-424
participants (3)
-
Adrian Schröter -
Olaf Hering -
Stefan Bruens