On Sun, Jul 31, 2016 at 6:47 AM, Peter Humphrey <pe...@prh.myzen.co.uk> wrote:
> > How is it possible for genlop's reported ETA to increase while its time > spent so far also increases? Could the concurrent gnutls merging have > affected it? Surely not. I've noticed the same oddity recently while building a couple of new amd64 boxes. Unfortunately, I can't document my observations with precise numbers, but I have noticed it on multiple occasions when simultaneously emerging, say, two packages that each take hours to build. As an example, If the estimate for the remaining time was another 1/2-1 hr while the 2d build was sharing system resources with the 1st, I've seen the 2d build estimate jump to 1-2 hr when having exclusive access to system resources after the 1st finishes. It's almost as if somewhere in the code there's logic that estimates time remaining as proportional to available system resources available instead of inversely proportional. This isn't a subtle anomaly, in my opinion. I've used genlop in this way to monitor build times for ages and I've never seen it behave this way before. And I haven't changed my build options by fooling around with -jN or by trying to do other things on the system while emerging. New behavior for genlop, or a 32/64 bit thing? (I've recently gone 64 bit and that's where I see the discrepancy.) Glad to see that someone else has experienced the same thing, and I'm not going crazy (although some might argue this is hardly proof...) John Blinka
