On Wed, 2007-09-19 at 03:59 +0200, Michael Schwendt wrote: > On Sat, 08 Sep 2007 11:01:24 +0200, Frank Büttner wrote: > > > Michael Schwendt schrieb: > > > On Sat, 08 Sep 2007 09:36:21 +0200, Frank Büttner wrote: > > > > > >> Hello, > > >> something with the build system is wrong. > > >> The build self will work, but the system says failed. > > >> Have anyone see this also? > > >> > > >> Build ID: 36210 and 36211. > > > > > > It has been a topic on fedora-maintainer multiple times. Here's the > > > corresponding ticket: > > > > > > https://hosted.fedoraproject.org/projects/fedora-infrastructure/ticket/125 > > > > > > > Yes, it's my problem too. I hope it will be fixed soon. > > Consider this fixed [1]. Resubmit your failed build-jobs for Extras > and EPEL and see. > > After I'd noticed that approx. 5 out of 6 noarch build-jobs on the > ppc2 server failed with the same symptoms, I've picked yum-cron as a > test pkg for an online-debugging session on the ppc2 host. As another > pkg that had failed very often, I've tested the final patch with > ctapi-common. > > The reason for failure was a race condition between plague 0.4.4.1 and > mock. The plague builder did not monitor the mock state accurately > enough. Mock could change its state (e.g. from prepping/setup to > building) while the plague builder was sleeping. In the cases I've > observed, mock had exited already when plague woke up and made a wrong > assumption about the state mock was in when it exited. > > [1] http://home.arcor.de/ms2002sep/tmp/plague-0.4.4.1-racecondition.patch Workaround looks sane, diagnosis is correct, thanks for tracking this down and fixing it. Out of curiosity, did a mock update or a hardware change exacerbate the issue? We only just started seeing this after ~2 years of using plague. Dan -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
