Bug 180634 – genlop - too short merge time during parallel emerge

• Product: Portage Development
• Status: RESOLVED DUPLICATE

[Description Bogatyrjov Kirill 2007-06-02 11:51:52 UTC]

Not sure if its correct place to report, but homepage listed in ebuild is not available at http://pollycoke.org/genlop.html

Genlop gives incorrect output on 
Boger linux # genlop -c

 * sys-libs/glibc-2.5-r3

       current merge time: 12 minutes and 59 seconds.
       ETA: 48 minutes and 54 seconds.
Boger linux # genlop -c

 * x11-drivers/nvidia-drivers-1.0.9755-r1

       current merge time: 13 seconds.
       ETA: 1 minute and 5 seconds.

 * sys-libs/glibc-2.5-r3

       current merge time: 13 minutes and 6 seconds.
       ETA: any time now.

Boger linux # genlop -v
genlop 0.30.4



Reproducible: Always

Steps to Reproduce:
1.Emerge glibc
2.emerge any package with known build time.




Boger linux # genlop -te glibc
 * sys-libs/glibc

     Sat Dec 23 18:11:56 2006 >>> sys-libs/glibc-2.4-r4
       merge time: 58 minutes and 17 seconds.

     Sat Feb 17 15:12:31 2007 >>> sys-libs/glibc-2.5
       merge time: 1 hour, 9 seconds.

     Sun May  6 17:03:29 2007 >>> sys-libs/glibc-2.5-r2
       merge time: 1 hour, 7 minutes and 15 seconds.

I've run another emerge, to check if it specific to nvidia-drivers
and i've got following result 

Boger linux # genlop -c

 * sys-libs/glibc-2.5-r3

       current merge time: 11 minutes and 4 seconds.
       ETA: 50 minutes and 49 seconds.
Boger linux # genlop -c

 * sys-libs/glibc-2.5-r3

       current merge time: .
       ETA: 1 hour, 1 minute and 53 seconds.
Boger linux # genlop -c

 * sys-libs/glibc-2.5-r3

       current merge time: 10 seconds.
       ETA: 1 hour, 1 minute and 43 seconds.
Running emerge of new package:

Boger linux # genlop -c

 * sys-libs/glibc-2.5-r3

       current merge time: 14 minutes and 42 seconds.
       ETA: 47 minutes and 11 seconds.
Boger linux # genlop -c

 * net-misc/neon-0.26.1-r1

       current merge time: 4 seconds.
       ETA: unknown.

 * sys-libs/glibc-2.5-r3

       current merge time: 14 minutes and 45 seconds.
       ETA: 47 minutes and 8 seconds.
But running with known build time:
Boger linux # genlop -c

 * sys-libs/glibc-2.5-r3

       current merge time: 21 minutes and 1 second.
       ETA: 40 minutes and 52 seconds.
Boger linux # genlop -c

 * games-simulation/openttd-0.5.2

       current merge time: 5 seconds.
       ETA: 2 minutes and 28 seconds.

 * sys-libs/glibc-2.5-r3

       current merge time: 21 minutes and 27 seconds.
       ETA: 16 minutes and 42 seconds.

Running other emerges (not glibc) in parallel don't reproduce problem, but merge time was around 2-3 minutes.
with long merge time:
Boger linux # genlop -c

 * kde-base/kdelibs-3.5.5-r10

       current merge time: 23 seconds.
       ETA: 1 hour, 10 minutes and 47 seconds.

 * dev-libs/glib-2.12.11

       current merge time: 6 seconds.
       ETA: 45 minutes and 22 seconds.
Boger linux # genlop -c

 * dev-libs/glib-2.12.11

       current merge time: 18 seconds.
       ETA: 2 minutes and 20 seconds.
                  
I'm not programmer, just user :) so what additional info you need?
I can email /var/log/emerge.log on separate request.

[Comment 1 Marius Mauch (RETIRED) 2007-06-02 12:06:25 UTC]

*** Bug 180632 has been marked as a duplicate of this bug. ***

[Comment 2 Bogatyrjov Kirill 2007-06-02 12:20:27 UTC]

(In reply to comment #1)
> *** Bug 180632 has been marked as a duplicate of this bug. ***
> 
Sorry for duble posting.

Update, it's not glibc specific.

Boger ~ # genlop -c

 * app-emulation/wine-0.9.38

       current merge time: 6 minutes and 4 seconds.
       ETA: 26 minutes and 8 seconds.
Boger ~ # genlop -c

 * dev-libs/glib-2.12.11

       current merge time: 5 seconds.
       ETA: 2 minutes and 32 seconds.

 * app-emulation/wine-0.9.38

       current merge time: 6 minutes and 7 seconds.
       ETA: 11 minutes and 17 seconds.

[Comment 3 Jakub Moc (RETIRED) 2007-06-02 12:20:34 UTC]

*** This bug has been marked as a duplicate of bug 154386 ***

*** This bug has been marked as a duplicate of bug 154386 ***