After doing an emerge -uD world or something, if a package fails, it is only obvious if I scroll up above all the ebuild messages to the error. The error *or at least recognition that x package failed) should be shown below the ebuild messages. Reproducible: Always Steps to Reproduce: 1. emerge -e world 2. have a package fail 3. you wont know until you scroll up, that's if you do. Actual Results: error way at the top Expected Results: error at the bottom
This should mostly be solved by the fix for bug #197905. However, if the merge is killed by a sandbox violation then there is no die message logged via eerror. In this case, an "ACCESS VIOLATION SUMMARY" is displayed bug not logged, and it can be obscured by elog messages that are displayed after it. Perhaps this is the case you are referring to?
I've just noticed that the logging behavior varies depending on whether or not the --buildpkg option is enabled, so that could be be something you noticed (more specific example would help).
Created attachment 154403 [details, diff] make sure elog messages always get collected If this patch is saved as /tmp/elog.patch, then it can be applied as follows: patch /usr/lib/portage/bin/emerge /tmp/elog.patch
This is fixed in 2.1.5.3.
