On 06/01/2024 00:54, John Blinka wrote:
I’ve often found that it gives one estimate when multiple packages are
being built, then a much longer estimate for still-in-progress builds
once some of the builds have finished.
That result defies common sense. Less remaining work has to take less,
not more (much more), time.
Common sense isn't common and, well, often doesn't make sense.
If there's a bunch of small builds skewing the "time per build" estimate
down, as they drop off the list the estimated time per build will go up,
and if the skew is serious enough it can even make the total estimated
time go up ...
Cheers,
Wol
