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 changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|Normal |Enhancement
Status|NEW |NEEDINFO
Info Provider| |mls@novell.com
--- Comment #1 from Susanne Oberhauser 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.
