http://bugzilla.suse.com/show_bug.cgi?id=1042558
http://bugzilla.suse.com/show_bug.cgi?id=1042558#c1
Lukas Ocilka changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |okurz@suse.com
Flags| |needinfo?(okurz@suse.com)
--- Comment #1 from Lukas Ocilka ---
## Observation
There are two sets of tests in this bugreport
## Expectations
One set per bugreport
## More details
### Test Run 6558
There is an error reported to the user: Not enough disk space
http://lord.arch/tests/6558#step/installation_overview/3
No, you can't continue before fixing the problem
http://lord.arch/tests/6558#step/start_install/3
--> IMO behaves correctly, error does not let you continue
### Test Run 6559
There is a warning that it might not fit, but openQA test continues
http://lord.arch/tests/6559#step/installation_overview/3
RPM starts reporting errors, but that a common stderr, so it might be warning,
it might be anything, it's reported to the user, but RPM does not report a
failure (exit code) http://lord.arch/tests/6559#step/install_and_reboot/17
Or is this from libzypp running scripts directly?
Then it fails hard, when RPMDB2SOLV finally reports an error with a different
exit code http://lord.arch/tests/6559#step/install_and_reboot/21
--> IMO Yast behaves correctly, you have been warned, you decided to
continue, but then it failed
--> Yes, we could change Yast to start screaming when there is only, let's
say 10% left, or 15% left, or 20% or 55% ... the fact is, there is
nothing like a good number, and even btrfs experts don't know
--> The only thing that should be fixed is IMO RPM (scripts) to throw
a real error when "no space left on device" appears somehow, but that
might be also just the "xterm" post-script issue (ignoring errors) see
http://lord.arch/tests/6559#step/install_and_reboot/17
So, what do you feel needs to be fixed?
--
You are receiving this mail because:
You are on the CC list for the bug.
