[Bug 430909] New: [openSUSE:Tools:Devel/obs-all-svn] Build fails if / tmp is full, without any message
https://bugzilla.novell.com/show_bug.cgi?id=430909 Summary: [openSUSE:Tools:Devel/obs-all-svn] Build fails if /tmp is full, without any message Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: BuildService AssignedTo: froh@novell.com ReportedBy: mopp@gmx.net QAContact: adrian@novell.com Found By: System Test Hello, I just tested the obs on my server. Version: obs-api-1.1.0.5190S The build just stops if /tmp/root_1 is running out of space. As you can see in my build log, there is not hint, about a full /tmp/root_1 (in my case 15MB were left). After adding some space the build worked. Possible solution: do a df from time to time and print a warning. My build log Memory limit set to 1373984KB Using BUILD_ROOT=/tmp/root_1 [...] Installing new /etc/nntpserver Executing /sbin/conf.d/SuSEconfig.perl... Executing /sbin/conf.d/SuSEconfig.permissions... Executing /sbin/conf.d/SuSEconfig.sortpasswd... Executing /sbin/conf.d/SuSEconfig.zmessages... Finished. ----------------------------------------------------------------- I have the following modifications for sles-release.spec: 19c19 < Release: 15.35 ---
Release: 15.1
----- building sles-release.spec (user abuild) ----------------------------------------------------------------- ----------------------------------------------------------------- + exec rpmbuild -ba --define '_srcdefattr (-,root,root)' /usr/src/packages/SOURCES/sles-release.spec Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.39610 Processing files: sles-release-10-15.1 error: File not found: /var/tmp/sles-release-10-build/etc/SuSE-release error: File not found: /var/tmp/sles-release-10-build/etc/motd error: File not found: /var/tmp/sles-release-10-build/etc/issue error: File not found: /var/tmp/sles-release-10-build/etc/issue.net RPM build errors: File not found: /var/tmp/sles-release-10-build/etc/SuSE-release File not found: /var/tmp/sles-release-10-build/etc/motd File not found: /var/tmp/sles-release-10-build/etc/issue File not found: /var/tmp/sles-release-10-build/etc/issue.net -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=430909 User froh@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=430909#c1 Susanne Oberhauser <froh@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Enhancement Status|NEW |NEEDINFO Info Provider| |mls@novell.com --- Comment #1 from Susanne Oberhauser <froh@novell.com> 2008-10-01 09:17:31 MDT --- So the build fails for lack of disk space, and this problem is not obvious from the build log. Hmmm. I'm actually not sure we can do much usefully in this regard, simply because Linux has not much to offer to trace or watchdog process or process group disk usage. Polling df also does not look like a good cure to me as builds may 'breathe' in their disk space usage, so they release claimed space (unlinking the files, aka 'rm') and then reclaim more space. What _could_ be usefull though is setting errexit and pipefail (see bash(1) ) in the spec file sections (prep, build, install, clean) and giving an obvious message in case of failure. Then the pacakge maintainer has to consciously ignore command failures, like this: dosomethingthatmayfail || true #make it fail silently But I _wonder_ wether this is worth the pain: The build fails, after all. So nothing is lost. The out-of-diskspace problem identifies itself by random failures at random places during the builds. Michael, do we have plans on becoming stricter and noisyer on failures during builds? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=430909 User mopp@gmx.net added comment https://bugzilla.novell.com/show_bug.cgi?id=430909#c2 --- Comment #2 from Ulf - <mopp@gmx.net> 2008-10-01 12:52:55 MDT --- I don' t think, that modifications to the spec file are a good idea. Just another simple idea. In case of an error of rpmbuild or during the setup of the chroot environment you may print one line with the df stats. I understand the problem to get a more detailed log and yes, it maybe not worth the time. At least at the moment, as there some more important thins to do. What' s about documentation of the obs, where to find a more detailed documentation or how to submit a documentation? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com