On Sunday 31 Jul 2016 10:48:33 Fernando Rodriguez wrote: > On 07/31/2016 06:47 AM, Peter Humphrey wrote: > > I've just encountered something I can't explain. Can anyone here? > > > > ~ $ genlop -c -f /mnt/rescue/var/log/emerge.log > > using logfile /mnt/rescue/var/log/emerge.log > > Currently merging 281 out of 287 > > * net-libs/gnutls-3.3.24 > > current merge time: 1 minute and 44 seconds. > > ETA: less than a minute. > > Currently merging 264 out of 287 > > > > * sys-devel/gcc-4.9.3 > > current merge time: 7 minutes and 12 seconds. > > ETA: 3 minutes and 13 seconds. > > > > $ genlop -c -f /mnt/rescue/var/log/emerge.log > > using logfile /mnt/rescue/var/log/emerge.log > > Currently merging 264 out of 287 > > * sys-devel/gcc-4.9.3 > > current merge time: 15 minutes and 19 seconds. > > ETA: 3 minutes and 41 seconds. > > > > How is it possible for genlop's reported ETA to increase while its time > > spent so far also increases?
...or to change at all, for that matter. > It is an estimate (a prediction) so it's subject to change. Yes, but the estimate is derived from an average of the durations found in the log file, so it can't change until the emerge is complete. > > Could the concurrent gnutls merging have affected it? Surely not. > > Probably, I don't know if genlop takes that into account. But there's > countless factors that affect build time that it's practically impossible > to predict accurately. So it means nothing. I think that's too pessimistic. If all your emerges have -j1, the accuracy is pretty good, or it used to be in the days when I did that. The major factor affecting the durations nowadays is -j > 1, so any other packages could be emerging at the same time, thus skewing the log record. Another, even bigger log skewer is my practice, if I need an emerge -e, of doing it in two stages: -eB first, then reboot to a minimal system and -eK. That avoids things like kdelibs being different when I come to reboot the system next time and hanging up during shutdown. > Does that estimate even look reasonable to you? > gnutls compiles in a few minutes but gcc takes significantly longer for > me. No, as I said, genlop's own estimates are poor nowadays, but I can make a rough estimate myself from comparing "genlop -c" with "genlop -t <package> | grep minutes". -- Rgds Peter
