[opensuse-buildservice] Can we fix the Tumbleweed builds
Tumbleweed hasn't built for days. It seems to have an incredibly low priority, so it mostly gets one or no build jobs and there's something changing in Factory that's causing it to require almost a complete rebuild every couple of days meaning it hasn't really been making much progress. Could we update it to a higher priority and allow it to use more build jobs so it has a chance of completing a build before the next update? Thanks, James -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Quoting James Bottomley <James.Bottomley@HansenPartnership.com>:
Tumbleweed hasn't built for days. It seems to have an incredibly low priority, so it mostly gets one or no build jobs and there's something changing in Factory that's causing it to require almost a complete rebuild every couple of days meaning it hasn't really been making much progress. Could we update it to a higher priority and allow it to use more build jobs so it has a chance of completing a build before the next update?
Changes in Factory do not trigger rebuilds in Tumbleweed; TW is based on openSUSE 12.3. A lot of resource is likely allocated at the moment to openSUSE:13.1; which, as some might argue, is about the flagship of where resources should go at this moment. Besides that, a lot of repos seem to have started 13.1 as build target, putting another large strain on the workers. There are currently > 50'000 build jobs pending, and I don't think changing prio of anything makes the list get any shorter in a different way than it does at the moment. We're just hit by the success of OBS itself: too many packages to be built for too many targets. Dominique -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thu, Oct 03, 2013 at 04:53:57PM +0200, Dominique Leuenberger a.k.a. Dimstar wrote:
Quoting James Bottomley <James.Bottomley@HansenPartnership.com>:
Tumbleweed hasn't built for days. It seems to have an incredibly low priority, so it mostly gets one or no build jobs and there's something changing in Factory that's causing it to require almost a complete rebuild every couple of days meaning it hasn't really been making much progress. Could we update it to a higher priority and allow it to use more build jobs so it has a chance of completing a build before the next update?
Changes in Factory do not trigger rebuilds in Tumbleweed; TW is based on openSUSE 12.3.
Yes, sorry, something is changing in 12.3-updates that is causing Tumbleweed rebuilds, which is normal, and annoying :)
A lot of resource is likely allocated at the moment to openSUSE:13.1; which, as some might argue, is about the flagship of where resources should go at this moment.
Even if Tumbleweed has a higher build priority of personal builds? I've been able to get personal packages build almost instantly yesterday, no delay from the scheduler at all, while Tumbleweed is still stalled. That implies something is up with the scheduler, right? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Quoting Greg KH <gregkh@linux.com>:
Even if Tumbleweed has a higher build priority of personal builds? I've been able to get personal packages build almost instantly yesterday, no delay from the scheduler at all, while Tumbleweed is still stalled. That implies something is up with the scheduler, right?
Well, looking at for example 13.1 build process: openSUSE:Factory => GNOME:Factory (devel) => home:xxx:branches:GNOME:Factory If want to commit a fix for Factory (and 13.1) I need it in my HOME branch, submit it to DEVEL, forward to Factory. What are the chances of getting a fix into 13.1 if HOME:* will get much lower prio and not have workers allocated? There is a finite amount of power available, which we are currently using to the max. Of course the one 'waiting' for the package is affected most. Shifting all the resources to that one will only mean somebody else has to wait, who in turn obviously considers his package 'worthier' to have more build power. In the end, the only thing that can help is throwing MORE power at it.. especially before a release this seems to become a repeating issue for us. Dominique -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Quoting Greg KH <gregkh@linux.com>:
On Thu, Oct 03, 2013 at 04:53:57PM +0200, Dominique Leuenberger a.k.a. Dimstar wrote:
Quoting James Bottomley <James.Bottomley@HansenPartnership.com>:
Tumbleweed hasn't built for days. It seems to have an incredibly low priority, so it mostly gets one or no build jobs and there's something changing in Factory that's causing it to require almost a complete rebuild every couple of days meaning it hasn't really been making much progress. Could we update it to a higher priority and allow it to use more build jobs so it has a chance of completing a build before the next update?
Changes in Factory do not trigger rebuilds in Tumbleweed; TW is based on openSUSE 12.3.
Yes, sorry, something is changing in 12.3-updates that is causing Tumbleweed rebuilds, which is normal, and annoying :)
so why do you build TW against :Update instead of openSUSE:12.3? Update channels are considered 'API/ABI' break free for openSUSE... and all the other stuff you have linked inside TW anyway, no? Dominique -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thu, Oct 03, 2013 at 05:56:16PM +0200, Dominique Leuenberger a.k.a. Dimstar wrote:
Quoting Greg KH <gregkh@linux.com>:
On Thu, Oct 03, 2013 at 04:53:57PM +0200, Dominique Leuenberger a.k.a. Dimstar wrote:
Quoting James Bottomley <James.Bottomley@HansenPartnership.com>:
Tumbleweed hasn't built for days. It seems to have an incredibly low priority, so it mostly gets one or no build jobs and there's something changing in Factory that's causing it to require almost a complete rebuild every couple of days meaning it hasn't really been making much progress. Could we update it to a higher priority and allow it to use more build jobs so it has a chance of completing a build before the next update?
Changes in Factory do not trigger rebuilds in Tumbleweed; TW is based on openSUSE 12.3.
Yes, sorry, something is changing in 12.3-updates that is causing Tumbleweed rebuilds, which is normal, and annoying :)
so why do you build TW against :Update instead of openSUSE:12.3?
Because sometimes we want to ensure updates rebuild things.
Update channels are considered 'API/ABI' break free for openSUSE...
Really? I have never heard this before, is it a guarantee?
and all the other stuff you have linked inside TW anyway, no?
What do you mean by "other stuff"? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Don, 2013-10-03 at 09:12 -0700, Greg KH wrote:
so why do you build TW against :Update instead of openSUSE:12.3?
Because sometimes we want to ensure updates rebuild things.
Update channels are considered 'API/ABI' break free for openSUSE...
Really? I have never heard this before, is it a guarantee?
It's probably not 100% true, but it would be close to impossible for ANY 3rd party if the :Update channel has an ABI incompatible change in libs.. There would be NO WAY for any 3rd party repo to work. on SLE, there is sort of a guarantee, on openSUSE it's a best effort of course.. nevertheless, I'm rather use the maintenance team still cares a lot for it (and if not, they should).
and all the other stuff you have linked inside TW anyway, no?
What do you mean by "other stuff"?
GLIB updates, KDE Updates, Kernel Updates... TW is supposed to be 'more update than <Release> + Update'. So frankly, I don't see much of a reason to build TW against the Update channel. Dominique -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thu, Oct 03, 2013 at 10:19:22PM +0200, Dimstar / Dominique Leuenberger wrote:
On Don, 2013-10-03 at 09:12 -0700, Greg KH wrote:
so why do you build TW against :Update instead of openSUSE:12.3?
Because sometimes we want to ensure updates rebuild things.
Update channels are considered 'API/ABI' break free for openSUSE...
Really? I have never heard this before, is it a guarantee?
It's probably not 100% true, but it would be close to impossible for ANY 3rd party if the :Update channel has an ABI incompatible change in libs.. There would be NO WAY for any 3rd party repo to work.
on SLE, there is sort of a guarantee, on openSUSE it's a best effort of course.. nevertheless, I'm rather use the maintenance team still cares a lot for it (and if not, they should).
and all the other stuff you have linked inside TW anyway, no?
What do you mean by "other stuff"?
GLIB updates, KDE Updates, Kernel Updates... TW is supposed to be 'more update than <Release> + Update'. So frankly, I don't see much of a reason to build TW against the Update channel.
For 12.1 and 12.2 I didn't do this, but changed to the update channel for 12.3 for some reason that I can't remember at the moment. So far it's been fine, with the exception of this last round of rebuilds. Oh well, I'll just wait, I'm patient... greg k-h -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thu, Oct 3, 2013 at 4:27 PM, Greg KH <gregkh@linux.com> wrote:
On Thu, Oct 03, 2013 at 10:19:22PM +0200, Dimstar / Dominique Leuenberger wrote:
On Don, 2013-10-03 at 09:12 -0700, Greg KH wrote:
so why do you build TW against :Update instead of openSUSE:12.3?
Because sometimes we want to ensure updates rebuild things.
Update channels are considered 'API/ABI' break free for openSUSE...
Really? I have never heard this before, is it a guarantee?
It's probably not 100% true, but it would be close to impossible for ANY 3rd party if the :Update channel has an ABI incompatible change in libs.. There would be NO WAY for any 3rd party repo to work.
on SLE, there is sort of a guarantee, on openSUSE it's a best effort of course.. nevertheless, I'm rather use the maintenance team still cares a lot for it (and if not, they should).
and all the other stuff you have linked inside TW anyway, no?
What do you mean by "other stuff"?
GLIB updates, KDE Updates, Kernel Updates... TW is supposed to be 'more update than <Release> + Update'. So frankly, I don't see much of a reason to build TW against the Update channel.
For 12.1 and 12.2 I didn't do this, but changed to the update channel for 12.3 for some reason that I can't remember at the moment. So far it's been fine, with the exception of this last round of rebuilds.
Oh well, I'll just wait, I'm patient...
greg k-h
Looks like the build farm caught up a couple days ago at least for a few hours. Did tumbl -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Ignore the last email, this one is complete On Wed, Oct 9, 2013 at 12:59 PM, Greg Freemyer <greg.freemyer@gmail.com> wrote:
On Thu, Oct 3, 2013 at 4:27 PM, Greg KH <gregkh@linux.com> wrote:
On Thu, Oct 03, 2013 at 10:19:22PM +0200, Dimstar / Dominique Leuenberger wrote:
On Don, 2013-10-03 at 09:12 -0700, Greg KH wrote:
so why do you build TW against :Update instead of openSUSE:12.3?
Because sometimes we want to ensure updates rebuild things.
Update channels are considered 'API/ABI' break free for openSUSE...
Really? I have never heard this before, is it a guarantee?
It's probably not 100% true, but it would be close to impossible for ANY 3rd party if the :Update channel has an ABI incompatible change in libs.. There would be NO WAY for any 3rd party repo to work.
on SLE, there is sort of a guarantee, on openSUSE it's a best effort of course.. nevertheless, I'm rather use the maintenance team still cares a lot for it (and if not, they should).
and all the other stuff you have linked inside TW anyway, no?
What do you mean by "other stuff"?
GLIB updates, KDE Updates, Kernel Updates... TW is supposed to be 'more update than <Release> + Update'. So frankly, I don't see much of a reason to build TW against the Update channel.
For 12.1 and 12.2 I didn't do this, but changed to the update channel for 12.3 for some reason that I can't remember at the moment. So far it's been fine, with the exception of this last round of rebuilds.
Oh well, I'll just wait, I'm patient...
greg k-h
Looks like the build farm caught up a couple days ago at least for a few hours. Did tumbleweed get fully built? If so, it looks like it has already started building again. Lots of scheduled and blocked packages. I looked at one that was built and I see this at the end of the build log: Retried build at Tue Apr 30 17:38:40 2013 returned same result, skipped Retried build at Fri May 3 18:10:11 2013 returned same result, skipped Retried build at Thu May 23 05:11:29 2013 returned same result, skipped Retried build at Sat Jun 15 11:32:13 2013 returned same result, skipped Retried build at Mon Jun 17 17:44:26 2013 returned same result, skipped Retried build at Wed Jun 19 14:16:05 2013 returned same result, skipped Retried build at Thu Jun 20 20:53:25 2013 returned same result, skipped Retried build at Wed Jul 3 04:48:48 2013 returned same result, skipped Retried build at Sat Jul 20 12:14:24 2013 returned same result, skipped Retried build at Mon Jul 22 19:54:10 2013 returned same result, skipped Retried build at Sun Aug 11 10:32:45 2013 returned same result, skipped Retried build at Mon Sep 2 14:45:15 2013 returned same result, skipped Retried build at Fri Sep 13 16:23:55 2013 returned same result, skipped Retried build at Tue Oct 1 02:15:10 2013 returned same result, skipped Retried build at Mon Oct 7 21:02:42 2013 returned same result, skipped I suspect that is lowing the priority of individual package builds like that, but then all packages dependent on ones like that one are delayed waiting on something like that to rebuild. Seems like tumbleweed never finishes building a full set of packages before an update to a core package restarts the whole process. Does the prioritization take into account the number of packages that are blocked based on the specific package in question? If not, should it? Greg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Wed, Oct 09, 2013 at 01:06:05PM -0400, Greg Freemyer wrote:
Ignore the last email, this one is complete
On Wed, Oct 9, 2013 at 12:59 PM, Greg Freemyer <greg.freemyer@gmail.com> wrote:
On Thu, Oct 3, 2013 at 4:27 PM, Greg KH <gregkh@linux.com> wrote:
On Thu, Oct 03, 2013 at 10:19:22PM +0200, Dimstar / Dominique Leuenberger wrote:
On Don, 2013-10-03 at 09:12 -0700, Greg KH wrote:
so why do you build TW against :Update instead of openSUSE:12.3?
Because sometimes we want to ensure updates rebuild things.
Update channels are considered 'API/ABI' break free for openSUSE...
Really? I have never heard this before, is it a guarantee?
It's probably not 100% true, but it would be close to impossible for ANY 3rd party if the :Update channel has an ABI incompatible change in libs.. There would be NO WAY for any 3rd party repo to work.
on SLE, there is sort of a guarantee, on openSUSE it's a best effort of course.. nevertheless, I'm rather use the maintenance team still cares a lot for it (and if not, they should).
and all the other stuff you have linked inside TW anyway, no?
What do you mean by "other stuff"?
GLIB updates, KDE Updates, Kernel Updates... TW is supposed to be 'more update than <Release> + Update'. So frankly, I don't see much of a reason to build TW against the Update channel.
For 12.1 and 12.2 I didn't do this, but changed to the update channel for 12.3 for some reason that I can't remember at the moment. So far it's been fine, with the exception of this last round of rebuilds.
Oh well, I'll just wait, I'm patient...
greg k-h
Looks like the build farm caught up a couple days ago at least for a few hours. Did tumbleweed get fully built?
Yes it did, it was "stable" for 2-3 days from what I can tell, before things started rebuilding yesterday.
If so, it looks like it has already started building again. Lots of scheduled and blocked packages.
I looked at one that was built and I see this at the end of the build log:
Retried build at Tue Apr 30 17:38:40 2013 returned same result, skipped Retried build at Fri May 3 18:10:11 2013 returned same result, skipped Retried build at Thu May 23 05:11:29 2013 returned same result, skipped Retried build at Sat Jun 15 11:32:13 2013 returned same result, skipped Retried build at Mon Jun 17 17:44:26 2013 returned same result, skipped Retried build at Wed Jun 19 14:16:05 2013 returned same result, skipped Retried build at Thu Jun 20 20:53:25 2013 returned same result, skipped Retried build at Wed Jul 3 04:48:48 2013 returned same result, skipped Retried build at Sat Jul 20 12:14:24 2013 returned same result, skipped Retried build at Mon Jul 22 19:54:10 2013 returned same result, skipped Retried build at Sun Aug 11 10:32:45 2013 returned same result, skipped Retried build at Mon Sep 2 14:45:15 2013 returned same result, skipped Retried build at Fri Sep 13 16:23:55 2013 returned same result, skipped Retried build at Tue Oct 1 02:15:10 2013 returned same result, skipped Retried build at Mon Oct 7 21:02:42 2013 returned same result, skipped
I suspect that is lowing the priority of individual package builds like that, but then all packages dependent on ones like that one are delayed waiting on something like that to rebuild. Seems like tumbleweed never finishes building a full set of packages before an update to a core package restarts the whole process.
Ah, interesting. I would love to not rebuild packages that don't need to but that's the big problem with dependancies and OBS, you really don't know if it needs to be rebuilt or not before you rebuild it to determine that :) As it is, it's ok for me, longer wait times for builds is normal at the end of the development cycle for a new openSUSE release, as more and more packages end up in Tumbleweed. After 13.1 is out, Tumbleweed will empty out, and all will be good for 3-5 months before KDE or GNOME releases a new version, and then this will start up all over again. thanks, greg k-h -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am 03.10.2013 17:40, schrieb Greg KH:
On Thu, Oct 03, 2013 at 04:53:57PM +0200, Dominique Leuenberger a.k.a. Dimstar wrote:
Quoting James Bottomley <James.Bottomley@HansenPartnership.com>:
Tumbleweed hasn't built for days. It seems to have an incredibly low priority, so it mostly gets one or no build jobs and there's something changing in Factory that's causing it to require almost a complete rebuild every couple of days meaning it hasn't really been making much progress. Could we update it to a higher priority and allow it to use more build jobs so it has a chance of completing a build before the next update?
Changes in Factory do not trigger rebuilds in Tumbleweed; TW is based on openSUSE 12.3.
Yes, sorry, something is changing in 12.3-updates that is causing Tumbleweed rebuilds, which is normal, and annoying :)
A lot of resource is likely allocated at the moment to openSUSE:13.1; which, as some might argue, is about the flagship of where resources should go at this moment.
Even if Tumbleweed has a higher build priority of personal builds? I've been able to get personal packages build almost instantly yesterday, no delay from the scheduler at all, while Tumbleweed is still stalled. That implies something is up with the scheduler, right?
Well, there are some things that work towards your personal packages: - source commits have a *much* higher priority than rebuilds - larger repos get a load penalty, so that smaller repos have a chance too - at the moment there are just a lot of small repos with source changes One thing that annoys me personally is that source changes in Kernel:HEAD trigger also rebuilds of all the obsolete branches, but all my delete requests for such projects are gently ignored. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Quoting Stephan Kulow <coolo@suse.de>:
Well, there are some things that work towards your personal packages: - source commits have a *much* higher priority than rebuilds - larger repos get a load penalty, so that smaller repos have a chance too - at the moment there are just a lot of small repos with source changes
One thing that annoys me personally is that source changes in Kernel:HEAD trigger also rebuilds of all the obsolete branches, but all my delete requests for such projects are gently ignored.
Ignored or declined? If ignored: use the 'trick' Adrian did last time for cleanup of old dists: with those magic 'auto-accept if not denied within 7 days deleterequests'. (we probably need a formal way for housekeeping at one point) Dominique -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Fri, 04 Oct 2013 10:44:36 +0200 Dominique Leuenberger <dominique@leuenberger.net> wrote:
gnored or declined? If ignored: use the 'trick' Adrian did last time for cleanup of old dists: with those magic 'auto-accept if not denied within 7 days deleterequests'.
(we probably need a formal way for housekeeping at one point)
That "trick" nearly caught me once because I was on a bike trip in my holidays. Pure luck one day was left when I started catching up with mail. 7 days is much too fast. (May be undelete is easy, but I don´t know and don´t want to spend the time to find out. It´s a spare time project for me.) Just my 2 cents. Detlef -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am 04.10.2013 10:44, schrieb Dominique Leuenberger:
Quoting Stephan Kulow <coolo@suse.de>:
Well, there are some things that work towards your personal packages: - source commits have a *much* higher priority than rebuilds - larger repos get a load penalty, so that smaller repos have a chance too - at the moment there are just a lot of small repos with source changes
One thing that annoys me personally is that source changes in Kernel:HEAD trigger also rebuilds of all the obsolete branches, but all my delete requests for such projects are gently ignored.
Ignored or declined? If ignored: use the 'trick' Adrian did last time for cleanup of old dists: with those magic 'auto-accept if not denied within 7 days deleterequests'.
I never seen one declined, it's mostly ignored. And I sure hope that auto-accept only works for admins/maintainers. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Quoting Stephan Kulow <coolo@suse.de>:
I never seen one declined, it's mostly ignored. And I sure hope that auto-accept only works for admins/maintainers.
Maybe, maybe not; but I guess you're right there.. but then, I'm sure Adrian is willing to help you with his admin powers to file those delete requests, if they are justified (which I am sure they are, coming from you). Still, in the end, it boils down to a clear defined process on how to get such things cleaned up. Dominique -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hi,
One thing that annoys me personally is that source changes in Kernel:HEAD trigger also rebuilds of all the obsolete branches, but all my delete requests for such projects are gently ignored.
I have the same issue (I've filed several delete requests against completely pointless branch projects (no source changes) of high-frequently-changing devel projects), but those are completely ignored. is it possible that perhaps Hermes is not sending out notifications for deleterequests by default? Thanks, Dirk -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am Montag, 7. Oktober 2013, 11:58:51 schrieb Dirk Müller:
Hi,
One thing that annoys me personally is that source changes in Kernel:HEAD trigger also rebuilds of all the obsolete branches, but all my delete requests for such projects are gently ignored.
I have the same issue (I've filed several delete requests against completely pointless branch projects (no source changes) of high-frequently-changing devel projects), but those are completely ignored. is it possible that perhaps Hermes is not sending out notifications for deleterequests by default?
I can testify that delete requests are sent. But maybe they are not read, or don't arrive at all? Maybe hermes could get a "delete request returns with 'no such user' means 'yes go ahead and delete'"- feature. Cheers MH -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Dirk Müller <dirk@dmllr.de> writes:
is it possible that perhaps Hermes is not sending out notifications for deleterequests by default?
Are *any* hermes notifications configured by default? Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am 07.10.2013 12:22, schrieb Andreas Schwab:
Dirk Müller <dirk@dmllr.de> writes:
is it possible that perhaps Hermes is not sending out notifications for deleterequests by default?
Are *any* hermes notifications configured by default?
Well, yes and no. There is code in the API to register Hermes feeds on initial login - but the code is not working for a year or so ;( Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am 07.10.2013 11:58, schrieb Dirk Müller:
Hi,
One thing that annoys me personally is that source changes in Kernel:HEAD trigger also rebuilds of all the obsolete branches, but all my delete requests for such projects are gently ignored.
I have the same issue (I've filed several delete requests against completely pointless branch projects (no source changes) of high-frequently-changing devel projects), but those are completely ignored. is it possible that perhaps Hermes is not sending out notifications for deleterequests by default?
Well, I get these emails and my hermes configuration is not so special. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thu, Oct 3, 2013 at 10:09 AM, James Bottomley <James.Bottomley@hansenpartnership.com> wrote:
Tumbleweed hasn't built for days. It seems to have an incredibly low priority, so it mostly gets one or no build jobs and there's something changing in Factory that's causing it to require almost a complete rebuild every couple of days meaning it hasn't really been making much progress. Could we update it to a higher priority and allow it to use more build jobs so it has a chance of completing a build before the next update?
Just 3 days ago the queue was down to 10,000 jobs outstanding. There are about 300 concurrent builds, so that is a manageable number. Did tumbleweed not get a lot of builds then? Looking at the current status by Project I don't see anything tumbleweed related building at all. That does seem wrong considering openSUSE 13.1 has about 30 concurrent builds on the intel servers right now. Greg -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thu, Oct 03, 2013 at 11:28:55AM -0400, Greg Freemyer wrote:
On Thu, Oct 3, 2013 at 10:09 AM, James Bottomley <James.Bottomley@hansenpartnership.com> wrote:
Tumbleweed hasn't built for days. It seems to have an incredibly low priority, so it mostly gets one or no build jobs and there's something changing in Factory that's causing it to require almost a complete rebuild every couple of days meaning it hasn't really been making much progress. Could we update it to a higher priority and allow it to use more build jobs so it has a chance of completing a build before the next update?
Just 3 days ago the queue was down to 10,000 jobs outstanding. There are about 300 concurrent builds, so that is a manageable number. Did tumbleweed not get a lot of builds then?
No it did not.
Looking at the current status by Project I don't see anything tumbleweed related building at all. That does seem wrong considering openSUSE 13.1 has about 30 concurrent builds on the intel servers right now.
And it also seems wrong given that about half of tumbleweed is currently in either "blocked" or "scheduled", with no packages actually building. That's a very strange state for it, given that it has (or had) a high build priority. Did something change with the scheduler? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thursday 2013-10-03 17:38, Greg KH wrote:
No it did not.
Looking at the current status by Project I don't see anything tumbleweed related building at all. That does seem wrong considering openSUSE 13.1 has about 30 concurrent builds on the intel servers right now.
And it also seems wrong given that about half of tumbleweed is currently in either "blocked" or "scheduled", with no packages actually building. That's a very strange state for it, given that it has (or had) a high build priority.
Well, if glibc had a rebuild (and it _did_ in openSUSE:12.3:Update), then anything depending on it will be blocked for a while, also because the toolchain depends on the toolchain itself.. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (12)
-
Andreas Schwab -
Detlef Steuer -
Dimstar / Dominique Leuenberger -
Dirk Müller -
Dominique Leuenberger -
Dominique Leuenberger a.k.a. Dimstar
-
Greg Freemyer -
Greg KH -
James Bottomley -
Jan Engelhardt -
Mathias Homann -
Stephan Kulow