Bug 686144 – app-portage/genlop-0.30.10-r2 computes times wrongly

• Status: UNCONFIRMED
• Product: Portage Development

[Description [e-mail] 2019-05-17 10:39:06 UTC]

I gog these figures this morning:

$ genlop -t rust -f /mnt/clrn/var/log/emerge.log | grep minute
       merge time: 38 minutes and 10 seconds.
       merge time: 32 minutes and 58 seconds.
       merge time: 32 minutes and 47 seconds.
       merge time: 30 minutes and 9 seconds.
       merge time: 40 minutes and 56 seconds.
       merge time: 54 minutes and 58 seconds.
$ genlop -c -f /mnt/clrn/var/log/emerge.log | grep minute
       current merge time: 16 minutes and 25 seconds.
       ETA: 2 minutes and 47 seconds.

Where did genlop get ~19 minutes from? The emerge was running in a chroot jail and my commands were issued from outside it.


Reproducible: Always

[Comment 1 [e-mail] 2019-05-17 10:40:12 UTC]

Created attachment 577038 [details]
emerge --info (outside the chroot)

[Comment 2 [e-mail] 2019-05-17 10:43:14 UTC]

"gog" => "got"

[Comment 3 [e-mail] 2019-05-17 13:04:32 UTC]

Created attachment 577040 [details]
emerge --info (inside the chroot)

[Comment 4 [e-mail] 2019-06-02 13:45:00 UTC]

This may be the same as bug 667534. It could be that genlop included the emerge times for virtual/rust in calculating the average time for dev-lang/rust.