http://bugzilla.novell.com/show_bug.cgi?id=521022 User adrian@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=521022#c1 --- Comment #1 from Adrian Schröter 2009-07-10 06:56:49 MDT --- This is caused to some degree on lack of build resources. There is also the plan to implement a "BUILD NOW, DESPITE OF OTHER PACKAGES" event, which will help to some degree and on the other hand increase the problem of build resources. Anyway, packagers can still work with "osc build" like in the old days with autobuild to build at any times. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=521022 User binner@kde.org added comment http://bugzilla.novell.com/show_bug.cgi?id=521022#c3 Stephan Binner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |jpr@novell.com --- Comment #3 from Stephan Binner 2009-09-05 03:04:36 MDT --- Isn't http://lizards.opensuse.org/2009/09/02/building-against-opensusefactory/ the solution? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=521022 User mmeeks@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=521022#c5 --- Comment #5 from Michael Meeks 2009-09-07 02:48:17 MDT --- Oh, and it's worse than comment #2 - since if you introduce a new dependency, until it has built on the server - there is no dependency information - so you simply can't build the dependant (server side dep resolution) - well, of course with some evil --no-init, hacking the local spec file to remove the dependency, chrooting into the jail, and installing the locally built package - you can overcome that [ here speaks the voice of long-suffering ;-], but this is not an elegant solution :-) It seems to me that much of the problem is/was in the scheduler which doesn't scale well; this seems to be the primary cause of other things not building: that the scheduler is simply wedged and not responding. I imagine at those times the CPU horsepower is also not doing much, so more CPUs seems like it simply won't help here. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=521022 User mmeeks@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=521022#c7 --- Comment #7 from Michael Meeks 2009-09-07 03:14:04 MDT --- This is not a request to build __NOW__ it is a request to build in a reasonably predictable fashion; I can't ask for a < 1 second build time for OO.o, but neither we building OO.o in this case :-) What do you believe is a reasonable median and maximum latency, having submitted a simple package to build, to getting to a 'finished' state in obs - (of course in the presence of an Factory re-build). Is the reasonable maximum: a) one hour b) four hours c) one working day d) four working days e) more ? f) no maximum - the sky is the limit :-) Being able to predict how long a given step will take, is rather a useful tool. To use your gcc analogy; if - each time you ran 'gcc' it took a non-deterministic time to compile a module: between milliseconds and days - and it also randomly aborted the build on every 10th run or so - would you love that tool ? :-) The request is fairly clear - OBS should not be useless for days when a factory re-build is happening; is that really a "WORKS FOR ME" - ie. it's not useless for you ? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=521022 User adrian@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=521022#c9 --- Comment #9 from Adrian Schröter 2009-09-07 03:26:27 MDT --- Something what makes more sense to me, would be a dedicated build instance for you, where you have garantied resources. We can talk about to make it easier to install one for you. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=521022 User jpr@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=521022#c11 JP Rosevear changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |abockover@novell.com --- Comment #11 from JP Rosevear 2009-09-08 04:22:25 MDT --- (In reply to comment #9)

Something what makes more sense to me, would be a dedicated build instance for you, where you have garantied resources.

We can talk about to make it easier to install one for you.

We already built our own in the Cambridge office because of this.(In reply to comment #10)

Currently the Server Status page of OBS has the information of an "Average Job time". I think this a first step for what Michael is asking for: Information on how long it will take at the moment to build his package. Michael, what do you think?

Right now this is at 8 hours for i586... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.