Checking for 12 GiB before build chromium is not sufficient. Chromium needs something between 12-14 GiB otherwise the check pass but the build fails in some cases. The problem can be solved when increasing the disk space but the check is not correct. Reproducible: Always Steps to Reproduce: 1. Have little disk space, but more than required 12GiB 2. Build chromium Actual Results: The ebuild phase 'unpack' has exited unexpectedly. his type of behavior is known to be triggered by things such as failed variable assignments (bug #190128) or bad substitution errors (bug #200313). Normally, before exiting, bash should have displayed an error message above. If bash did not produce an error message above, it's possible that the ebuild has called `exit` when it should have called `die` instead. This behavior may also be triggered by a corrupt bash binary or a hardware problem such as memory or cpu malfunction... Expected Results: Checking for disc space should fail.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=38cd1b9aab88407062c413cdee5e3349156ba276 commit 38cd1b9aab88407062c413cdee5e3349156ba276 Author: Stephan Hartmann <sultan@gentoo.org> AuthorDate: 2023-07-14 11:46:10 +0000 Commit: Stephan Hartmann <sultan@gentoo.org> CommitDate: 2023-07-14 11:46:10 +0000 www-client/chromium: beta channel bump to 115.0.5790.90 Increase required disk space a bit. Bug: https://bugs.gentoo.org/909742 Signed-off-by: Stephan Hartmann <sultan@gentoo.org> www-client/chromium/Manifest | 2 +- ....0.5790.56-r1.ebuild => chromium-115.0.5790.90.ebuild} | 15 +++++++-------- 2 files changed, 8 insertions(+), 9 deletions(-)
