genlop bugs about time?

madbiker · Posted: Sun Feb 13, 2005 1:45 am Post subject: genlop bugs about time?

So I was trying to use a genlop --current -n that my torsmo config would exec every once in a while so I could see info on what was building, how long it has been building, and how long it had left (approximately).

Then I noticed a little problem: I was emerging the new qt, and genlop --current showed about 4 hours left (for a total of 4.5 hours). This was consistant even after I killed the emerge and started it again. I then did a time emerge qt, and it came back at about 45 minutes. Then I did a genlop -i qt and it agreed that the average emerge time for qt was about 45 minutes.

Anyone know why --current is so off the real numbers? I know it's an estimate, but it's off by more than 400%!

brims · Guru Joined: 19 Apr 2004 Posts: 492 Location: Arizona

I've seen this with another package before, I think that a previous build might have been a lot more source to compile than the current one. Correct me if I'm wrong.

madbiker · Posted: Sun Feb 13, 2005 1:58 am Post subject:

Well my understanding was that when you asked for how long an emerge is going to take, genlop looks at any previous times you've emerged it, and figures out how long each one took, then averages. So, if you upgrade hardware or something, clearing your logs might be a good idea in order for genlop to work properly. That isn't the case here though.