[opensuse-buildservice] Build service bug.

I have three lilypond projects, one the parent, one is a branch and one is a link (home:plater lilypond). All of a sudden, after working fine since inception the branched project gives me a "broken: conflict in file lilypond.spec" error but if I look at the build log the package is building. Osc pull refuses to do anything (sorry I didn't save the output), osc up makes no difference and osc ci say's nothing to checkin. I delete the package and then branch again. At the time of branching lilypond is building in the parent, the x86_64 packages were previously failed for the last couple of builds and I know how to fix it and the current build is with the fix. After the new branch has completed, I have copies of the parents binaries from x86_64 only no i586 ones. This doesn't seem like normal behavior. The binaries that appeared are also marked as failed without any attempt to build even after the parent had built successfully. Maybe one shouldn't branch a package until it's stopped building? Or maybe this is work in progress, it would be nice if somebody acknowledged that :- a) This is unfixable and I must just work around it or b) We are aware of this problem and are busy fixing it or c) Thanks for letting us know. Glad to help Dave P -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On Wed, Jan 20, 2010 at 05:01:05PM +0200, Dave Plater wrote:
Maybe one shouldn't branch a package until it's stopped building?
No, branching is done source-wise, it has nothing to do with package building.
Or maybe this is work in progress, it would be nice if somebody acknowledged that :- a) This is unfixable and I must just work around it or b) We are aware of this problem and are busy fixing it or c) Thanks for letting us know.
There was a bug in the code that prevented the scheduler from detecting that a broken link is working again. Maybe you ran into it (it was fixed only yesterday). Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg 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 01/20/2010 05:34 PM, Michael Schroeder wrote:
On Wed, Jan 20, 2010 at 05:01:05PM +0200, Dave Plater wrote:
Maybe one shouldn't branch a package until it's stopped building?
No, branching is done source-wise, it has nothing to do with package building.
Or maybe this is work in progress, it would be nice if somebody acknowledged that :- a) This is unfixable and I must just work around it or b) We are aware of this problem and are busy fixing it or c) Thanks for letting us know.
There was a bug in the code that prevented the scheduler from detecting that a broken link is working again. Maybe you ran into it (it was fixed only yesterday).
Cheers, Michael.
This happened this morning about 10:30 UTC. The branch repo is still sitting with the failed builds and the binaries that appeared by magic like a snapshot of the state of the parent before I triggered a rebuild, just in case it can help track the bug. Maybe the spec file conflict that started yesterday was due to that? Regards Dave P -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
Dave Plater
-
Michael Schroeder