LP Build System should provide ETA

[Celso Providelo]

Developers claim for more useful information about when pending build will be processed, It can be estimated by:

{{{
SUM(last_duration of high_scored builds for this arch) / # of builders for this arch
}}}

We may save some time by caching IBuild.last_duration at the build record creation time, it can be also used to "progress-bar" the building jobs and lately for rescoring quickest builds first (if it makes any sense)

[Celso Providelo (cprov)]

Soyuz bug, it will be implemented in the buildd-master side.

[Celso Providelo (cprov)]

Just a consideration, we are interested in fact in two kinds of ETA:

 * how long a given pending build job will take to start being built and

 * how long a given building job will take to finish.

nothing new, just a clarification.

[Muharem Hrnjadovic (al-maisan)]

ETA => estimated build job dispatch time

[Jared Greenwald (jetsaredim)]

Just to add to this since the bug/enhancement I filed got made a dup of this - might as well list the info here for completeness... The things I was looking for are:

 * list of builds in a given wait queue
 * position of your build in that queue

Both of these are slightly different than the above mentioned items since they deal with builds that have yet to be started to build and are still in the queue.

[Muharem Hrnjadovic (al-maisan)]

Hello Jared,

thank you very much for commenting on this issue ..

Being able to see what builds are waiting in a particular queue as well as their positions may be helpful at times. However, I am afraid it is not really sufficient. Consider e.g. a scenario where

   - a build job (you are interested in) is in position 2 in the queue but
   - the job ahead of it (e.g. open office) takes a very long time to complete

You'll probably agree that knowing that your job is in position 2 of the queue is not really very meaningful.

That's why we plan to provide an estimated build job start time for all (pending) build jobs.

[Jared Greenwald (jetsaredim)]

Observations:

* obviously, my comment is a request so just something to consider and whatever you implement will be an improvement.
* I don't think the things I listed are necessarily in contrast to the enhancements listed in the original feature request. In fact, based on the description you just added, I think they would compliment each other. Maybe a list of all of the builds with time estimates associated with each and then an overall total.
* how are you going to calculate the estimated time of a given build? I would imagine that even if you had some cached data from previous builds of similarly named packages you could still be wildly off in your time estimate. (I guess is an estimate is still an estimate.)

[Muharem Hrnjadovic (al-maisan)]

Re. the calculation method for the estimated build job start time: we intend to use historical build durations for the same package where available.

If a package is to be built for the very first time, we don't have a historical build duration yet and hence need to make an educated guess :-)

As pointed out in the previous comments this is an _estimated_ build job start time -- you've been warned :-)

[Matthew Paul Thomas (mpt)]

Showing the build queue position, as opposed to the estimated time of completion, is bug 194265.

[Muharem Hrnjadovic (al-maisan)]

This is a soyuz feature.

[Muharem Hrnjadovic (al-maisan)]

RF 6086