I just wanted to try the tip of the week and I found this weird behavior. From the moment the compile time exceeds the expected one (that's my theory), the expected time jumps to weird numbers (4 minutes to 6 days). Console output below. I did not try to reproduce it root@shock louis # genlop --current * sys-devel/binutils-2.15.90.0.1.1-r3 current merge time: 42 seconds. ETA: 4 minutes and 10 seconds. root@shock louis # genlop --current * sys-devel/binutils-2.15.90.0.1.1-r3 current merge time: 5 minutes and 32 seconds. ETA: 6 days, 23 hours, 59 minutes and 21 seconds. Reproducible: Didn't try Steps to Reproduce: 1. 2. 3. Actual Results: See details... Expected Results: Keep same duration with note that time has exceeded expectation would make more sense.
If you are using version 0.30.2 upgrade to 0.30.3 Giorgio
same here (using genlop-0.30.2). Also the ETA time itself seems to be wrong as the previous merges suggest it would take about 30 min in total: $ genlop --current * mail-client/evolution-2.0.2-r1 current merge time: 15 minutes and 29 seconds. ETA: 2 minutes and 58 seconds. $ genlop --current * mail-client/evolution-2.0.2-r1 current merge time: 19 minutes and 11 seconds. ETA: 6 days, 23 hours, 59 minutes and 17 seconds. $ genlop -t evolution * mail-client/evolution Fri Nov 12 20:06:25 2004 >>> mail-client/evolution-2.0.2 merge time: 30 minutes and 54 seconds. Tue Dec 28 15:01:32 2004 >>> mail-client/evolution-2.0.2 merge time: 29 minutes and 49 seconds.
a update on 0.30.3 works fine
Re-open if you can reproduce with a recent genlop version.