Hi, I think it depends how much the estimation is wrong. If it says 10 minutes when it's 6 hours, I think it's not good. But if it says like 1 hour when it's 2, it might still be ok. At least it can help someone to decide whether it's worth waiting a few minutes/hours, or simply give up and check the next day. The time estimation for one package could be based on heuristics from its compile time history. For example, if after compliling a given package a few times we found out that it usually takes say 30 minutes to build successfully, then we can assume that in the future it will take almost as long, if not longer. Also like Doiggl said, it would be also good to know how many packages are in the queue. A value like "5234 packages scheduled to be built before yours, 1234 currently building" might do it. Vincent Andreas Jaeger a écrit :

On Friday 24 July 2009 07:56:16 Adrian Schröter wrote:

...

Am Freitag, 24. Juli 2009 07:11:13 schrieb doiggl@velocitynet.com.au:

...

Hello, When your project is blocked in the queue because it is waiting for something to build e.g(binutils) can a time estimate be given as to how long to wait before it may start processing - put that estimation on the 'Package AAA (Project BBB home:CCC)' page when you view the page. One could implement something, but it will not be very reliable, because the state and order can change with any further submission.

I suggest to file a feature request using features.opensuse.org.

But first:What to others think? Do you consider such an estimate ok? Or should we not publish anything since it might change too often?

Andreas

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org