Mailinglist Archive: opensuse-buildservice (375 mails)
| < Previous | Next > |
Re: [opensuse-buildservice] openSUSE:Tools:Unstable OBS svn trunc -r 3598 some testresults
- From: Martin Mohring <martin.mohring@xxxxxxxxx>
- Date: Tue, 01 Apr 2008 16:57:41 +0200
- Message-id: <47F24D65.5040505@xxxxxxxxx>
Hi Michael,
I have the impression that there is a concrete case where the endless rebuilds happen.
E.g. we have projects openSUSE:Tools and openSUSE:Tools:Unstable. openSUSE:Tools:Unstable uses for its build targets the underlying openSUSE:Tools build targets.
Lets take the build openSUSE:Tools:Unstable/rubygem-activesupport-2_0/Fedora_7/i586, which currently fails both in openSUSE:Tools and in openSUSE:Tools:Unstable.
It seems that restarting the scheduler can now trigger a build of openSUSE:Tools:Unstable/rubygem-activesupport-2_0/Fedora_7/i586 into an endless loop for some reason.
Both pkgs fail to build, but the scheduler decides to rebuild the pkg, which ends in a loop.
Martin
Martin Mohring wrote:
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
I have the impression that there is a concrete case where the endless rebuilds happen.
E.g. we have projects openSUSE:Tools and openSUSE:Tools:Unstable. openSUSE:Tools:Unstable uses for its build targets the underlying openSUSE:Tools build targets.
Lets take the build openSUSE:Tools:Unstable/rubygem-activesupport-2_0/Fedora_7/i586, which currently fails both in openSUSE:Tools and in openSUSE:Tools:Unstable.
It seems that restarting the scheduler can now trigger a build of openSUSE:Tools:Unstable/rubygem-activesupport-2_0/Fedora_7/i586 into an endless loop for some reason.
Both pkgs fail to build, but the scheduler decides to rebuild the pkg, which ends in a loop.
Martin
Martin Mohring wrote:
Martin Mohring wrote:
Hi,
Michael Schroeder wrote:
On Tue, Apr 01, 2008 at 03:00:23PM +0200, Martin Mohring wrote:Attached is the part which loops. Btw. openSUSE:Tools:Unstable is very similiar to that on build.o.o, especially the ruby pkgs are an exact copy of yours.
I checked that this is not the case. When I installed the new code, it triggered about 400 rebuild. They are finished after one day, only 3 remaining in a loop after 1 day of testing. Is there a log I can look for these things a search for your hint?
The scheduler output for those packages would be helpful.
To be 100% sure, I stop the complete OBS Server and Workers. Removed build-roots of Workers. And then restarted again. Lets see what happens.
The restart triggered now 2 completely other pkgs. One of them was in failed state before. I give you a complete dump of that, from the start of OBS.
Now you know everything of the projects in our OBS :-) Btw, ST Linux 2.2 and 2.3 are our crossbuild distros (they do not use the cross-build feature with another buildtarget we are working on, they do not modify the scheduler of yours - dont mind , we develop this in another OBS instance here).
Bye, Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
| < Previous | Next > |