The /var/log/emerge.log should be more transparent in case there are more parallel emerge activities. This might be the parallel fetching / merging / depency calculating / syncing whatever. Of course some of the activities might conflict and people may not use them together, but other activities don't conflict at all (i.g. fetching / merging). This time the log doesn't allow to idetify, which emerge session "terminated successfully" or what session "aborted". Maybe this misconception could be fixed using the timestamp at the beginning as session id, and could be added as additional information.
*** Bug 139873 has been marked as a duplicate of this bug. ***
i searched for parallel-fetch, couldn't find anything, posting my message from bug #139873 as well so other people can find this bug. if feature parallel-fetch is activated in portage an entry in the portagelogfile is created when fetching is finished <time>: *** terminating. this breaks logparsers because the same message apears when emerge failed and also when emerge finished. i suggest all <time>: *** terminating writing to the logfiles is replaced with actual events for example; succesfully downloaded sources, failed downloading sources, emerge failed prematurely or emerge is succesfully finished, etc. this would make logparsing a lot easier.
In svn r3833 I've added a hack for the parallel-fetch case. The rest of this bug may not get fixed for a while because parallel use of emerge isn't really supported.
The parallel-fetch fix is also in svn r4070 for 2.1-r2.
*** This bug has been marked as a duplicate of bug 147516 ***
