Am Freitag, 15. April 2011, 16:29:18 schrieb doiggl@velocitynet.com.au:

Hello, Can a 'job is nth in queue' indicator be added ot obs

The place in the que counts backwards in the following see sample [1] place in queue will count from 128 down to 0 When the place in queue changes to 0 change status to building.

[1] openSUSE_11.4 Build jobs exists x86_64 scheduled place in queue :128

Also you see if a queue is stuck or previous job is stalled if the place in queue has not changed.

We don't have such a queue. And if would have your job could easily moved back by some hundred numbers if a more important project repo suddenly decides to start to build. So I think such a number will cause more confusion then it helps. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Am Freitag, 15. April 2011, 09:04:02 schrieb Claudio Freire:

On Fri, Apr 15, 2011 at 8:35 AM, Adrian Schröter wrote:

...

We don't have such a queue. And if would have your job could easily moved back by some hundred numbers if a more important project repo suddenly decides to start to build.

So I think such a number will cause more confusion then it helps.

So, since we're in this matter of progress indicators, cmake projects output to stdout the build percentage. It ought to be a trivial matter parsing that percentage and adding it to the "building" state indicator, right?

That percentage is just for one call in a spec file and not a total number for entire build. Could create also confusion IMHO.

This would probably help on bigger projects that take long to build.

Status could be:

building - booting building - configure building - building 1% .. building - building 50% .. building - building 99% building - packaging building - signing success

:-)

-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Am Freitag, 15. April 2011, 09:10:48 schrieb Claudio Freire:

On Fri, Apr 15, 2011 at 9:07 AM, Adrian Schröter wrote:

...

That percentage is just for one call in a spec file and not a total number for entire build.

Could create also confusion IMHO.

True, but it's the most time-consuming part IMHO.

And I'm not saying that it should say "done" when it reaches 100%, only switch to "packaging".

well, I am happy about any patch you may write :) -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Fri, Apr 15, 2011 at 09:04:02AM +0200, Claudio Freire wrote:

On Fri, Apr 15, 2011 at 8:35 AM, Adrian Schröter wrote:

...

We don't have such a queue. And if would have your job could easily moved back by some hundred numbers if a more important project repo suddenly decides to start to build.

So I think such a number will cause more confusion then it helps.

So, since we're in this matter of progress indicators, cmake projects output to stdout the build percentage. It ought to be a trivial matter parsing that percentage and adding it to the "building" state indicator, right?

This would probably help on bigger projects that take long to build.

Status could be:

building - booting building - configure building - building 1% .. building - building 50% .. building - building 99% building - packaging building - signing success

How do you know ahead of time how long a build process takes, or what it even involves, in order to be able to determine where 50% is? Hint, you don't :( sorry, this isn't going to work. greg k-h -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Fri, Apr 15, 2011 at 11:57:00PM +0200, Claudio Freire wrote:

On Fri, Apr 15, 2011 at 7:10 PM, Greg KH wrote:

...

How do you know ahead of time how long a build process takes, or what it even involves, in order to be able to determine where 50% is?

While technically true, there's ways to approximate.

Really? How do you do so for something as "simple" as building the Linux kernel?

Since, technically, most files takes roughly the same amount of time to compile. And, technically, abnormally costly files tend to be randomly spread. So if you count percentage by number of tasks to run (number of files to build), it usually works out fine.

How can you count the number of files to build ahead of time? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Sat, Apr 16, 2011 at 11:34:52PM +0200, Claudio Freire wrote:

On Sat, Apr 16, 2011 at 12:45 AM, Greg KH wrote:

...

On Fri, Apr 15, 2011 at 11:57:00PM +0200, Claudio Freire wrote:

...

On Fri, Apr 15, 2011 at 7:10 PM, Greg KH wrote:

...

How do you know ahead of time how long a build process takes, or what it even involves, in order to be able to determine where 50% is?

While technically true, there's ways to approximate.

Really?  How do you do so for something as "simple" as building the Linux kernel?

...

Since, technically, most files takes roughly the same amount of time to compile. And, technically, abnormally costly files tend to be randomly spread. So if you count percentage by number of tasks to run (number of files to build), it usually works out fine.

How can you count the number of files to build ahead of time?

Any half-decent build system does a pre-pass to check for changes, dependencies, and what needs to be rebuilt. So yes, that's already done, and rather quickly.

Ok, nice, care to show how you would do this for the kernel package as an example? It has a very decent build system. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On 16.4.2011 23:34, Claudio Freire wrote:

On Sat, Apr 16, 2011 at 12:45 AM, Greg KH wrote:

...

How can you count the number of files to build ahead of time?

Any half-decent build system does a pre-pass to check for changes, dependencies, and what needs to be rebuilt. So yes, that's already done, and rather quickly.

Not really, many packages, including the linux kernel, don't use a single makefile, but rather build recursively. I think that cmake does first preprocess all cmake files and then generates one huge makefile, which then has information about all files to be build, but in general, you don't have this information. What could work to some extent is to compare the current build log and the last successful one. It wouldn't work for huge changes like kernel version updates, but otherwise, I think it could estimate the remaining time quite well. That could be a nice hackweek project :-) Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org