On Saturday, 6 January 2024 16:26:49 GMT Daniel Pielmeier wrote: > Am 5. Januar 2024 23:51:39 UTC schrieb Peter Humphrey <pe...@prh.myzen.co.uk>: > >Hello list, > > > >I've just had some strange output from genlop on my 16-thread i5 box, thus: > > > ># genlop -t libreoffice | /bin/grep minute > > > > merge time: 37 minutes and 38 seconds. > > merge time: 52 minutes and 59 seconds. > > merge time: 46 minutes and 17 seconds. > > > ># genlop -c > > > > Currently merging 11 out of 11 > > > > * app-office/libreoffice-7.5.9.2 > > > > current merge time: 4 minutes and 3 seconds. > > ETA: 1 hour, 4 minutes and 24 seconds. > > > >### Then, once the update finished: > > > ># genlop -t libreoffice | /bin/grep minute > > > > merge time: 37 minutes and 38 seconds. > > merge time: 52 minutes and 59 seconds. > > merge time: 46 minutes and 17 seconds. > > merge time: 38 minutes and 40 seconds. > > > >I know genlop is, shall we say, not perfect, but how can it be so grossly > >wrong as that? > > > >I have this in make.conf, and it hasn't changed since I built the machine: > > > >grep '\-j' /etc/portage/make.conf > >EMERGE_DEFAULT_OPTS="--jobs --load-average=12 > >MAKEOPTS="-j12 -l12" > > There are not by chance binary merges which took less than a minute? That > might explain the differences.
That would skew the prediction downwards, not up. > What is the output wihout the grep or filtering by merge time instead. The same. -- Regards, Peter.
