[opensuse-buildservice] Timeout for long running tasks
----- Message Text ----- Hello, At the moment there are many builds in "building but not doing anything" state. I think there should be two security mechanisms: a) Break broken builds after a specific time (2 hours? How long take kernel builds?) b) Allow the package owners/users to signal an abort build. c) When rebuild is triggered do abort build signal automatically as the build is discarded anyway (to save computing power). Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Mittwoch 14 Februar 2007 08:08:21 schrieb Dirk Stoecker:
----- Message Text ----- Hello,
At the moment there are many builds in "building but not doing anything" state.
I think there should be two security mechanisms:
a) Break broken builds after a specific time (2 hours? How long take kernel builds?)
possible idea, but the kernel is not the longest possible build. I have seen jobs taking > 12 hours for serious ...
b) Allow the package owners/users to signal an abort build.
might be a good idea, at least as long we also offer to trigger rebuilds.
c) When rebuild is triggered do abort build signal automatically as the build is discarded anyway (to save computing power).
IIRC this is already implemented -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, 14 Feb 2007, Adrian Schröter wrote:
a) Break broken builds after a specific time (2 hours? How long take kernel builds?)
possible idea, but the kernel is not the longest possible build. I have seen jobs taking > 12 hours for serious ...
Set the timeout to an hour and allow to specify longer timeouts for individual packages. There shoudn't be that many where this is required.
b) Allow the package owners/users to signal an abort build.
might be a good idea, at least as long we also offer to trigger rebuilds.
What's the option instead of "rebuild triggering" when you say "as long".
c) When rebuild is triggered do abort build signal automatically as the build is discarded anyway (to save computing power).
IIRC this is already implemented
In this case it does not work (I would think). But at the moment the buildservice anyway has some problems, so I'm not sure :-) - my pavuk package setpgrp() problem - my ntrip package uses old spec-file also after updating (for some distributions only) - hanging builds Ciao -- http://www.dstoecker.eu/ (PGP key available)
On Wed, Feb 14, 2007 at 08:08:21AM +0100, Dirk Stoecker wrote:
At the moment there are many builds in "building but not doing anything" state.
I think there should be two security mechanisms:
a) Break broken builds after a specific time (2 hours? How long take kernel builds?)
Already implemented and works well.
b) Allow the package owners/users to signal an abort build.
Also already implemented ;-)
c) When rebuild is triggered do abort build signal automatically as the build is discarded anyway (to save computing power).
Hey, this is your lucky day! It's implemented, too! What's missing is: d) periodically check if the client still builds the job, so that - jobs on dead clients will get restarted - clients that booted and now build different jobs are also taken care of Cheers, Michael. -- Michael Schroeder mls@suse.de main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, 14 Feb 2007, Michael Schroeder wrote:
On Wed, Feb 14, 2007 at 08:08:21AM +0100, Dirk Stoecker wrote:
At the moment there are many builds in "building but not doing anything" state.
I think there should be two security mechanisms:
a) Break broken builds after a specific time (2 hours? How long take kernel builds?)
Already implemented and works well.
Since yesterday or why have there been 24hour jobs?
b) Allow the package owners/users to signal an abort build.
Also already implemented ;-)
In the interfaces? webclient / osc ? Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, Feb 14, 2007 at 12:56:32PM +0100, Dirk Stoecker wrote:
On Wed, Feb 14, 2007 at 08:08:21AM +0100, Dirk Stoecker wrote:
At the moment there are many builds in "building but not doing anything" state.
I think there should be two security mechanisms:
a) Break broken builds after a specific time (2 hours? How long take kernel builds?)
Already implemented and works well.
Since yesterday or why have there been 24hour jobs?
Because of d)
b) Allow the package owners/users to signal an abort build.
Also already implemented ;-)
In the interfaces? webclient / osc ?
Support in the webclient/osc is still missing AFAIK. Cheers, Michael. -- Michael Schroeder mls@suse.de main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Wed, 14 Feb 2007, Michael Schroeder wrote:
c) When rebuild is triggered do abort build signal automatically as the build is discarded anyway (to save computing power).
Hey, this is your lucky day! It's implemented, too!
If it is implemented, then it is not working. I did checkin a new spec file for libsynaptics and ksynaptics in my home project (ksynaptics depends on libsynaptics). I did the checking in reverse order - first ksynaptics, then libsynaptics. - ksynaptics checking trigger rebuild and all rebuilds startet (seldomly, but buildservice had nothing to do :-) - libsynaptics triggered rebuild and all were set to scheduled. - ksynaptics were set to blocked due to libsynaptics. --> The running ksynaptics builds have not been cancelled even if the are totally useless. Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, Feb 20, 2007 at 10:49:58AM +0100, Dirk Stoecker wrote:
I did checkin a new spec file for libsynaptics and ksynaptics in my home project (ksynaptics depends on libsynaptics). I did the checking in reverse order - first ksynaptics, then libsynaptics.
- ksynaptics checking trigger rebuild and all rebuilds startet (seldomly, but buildservice had nothing to do :-) - libsynaptics triggered rebuild and all were set to scheduled. - ksynaptics were set to blocked due to libsynaptics.
--> The running ksynaptics builds have not been cancelled even if the are totally useless.
Yes, that's the way it works. Basically we can't decide that the old build is useless until the packages are built. What's implemented is that old builds get killed if the source is changed. Cheers, Michael. -- Michael Schroeder mls@suse.de main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (3)
-
Adrian Schröter -
Dirk Stoecker -
Michael Schroeder