On Tue, 2006-02-28 at 23:50 -0500, Dan Williams wrote: > On Wed, 2006-03-01 at 05:27 +0100, Ralf Corsepius wrote: > > On Tue, 2006-02-28 at 20:09 -0500, Dan Williams wrote: > > > On Wed, 2006-03-01 at 00:02 +0100, Ralf Corsepius wrote: > > > > On Tue, 2006-02-28 at 18:14 +0100, Thorsten Leemhuis wrote: > > > > > Hi! > > > > > > > > > > This is a script-generated mail to remind you that some of your arch- > > > > > specific Fedora Extras packages were not yet rebuild for FC5. All arch- > > > > > specific packages in "extras/development/" that were build before > > > > > > > > > '2006-02-13 02:48:00 -0500' > > > > > > > > > > should be rebuild as soon as possible. We're running out of time, FC5 > > > > > is near! > > > > > > > > I'd do, but ATM, I am facing sporadic > > > > ... > > > > Package ... enqueued. (However, no Job ID was provided in the time > > > > required) > > > > ... > > > > > > > > again (2 out of ca. 9 requests failed) > > > > > > > > <rant> > > > > IMO, such mass rebuild requests are not of much use before we have more > > > > reliable buildsystem. > > > > </rant> > > > > > > Build system seems to be doing fine ATM... > > > > It just happened again: > > > > Package perl-Test-ClassAPI enqueued. (However, no Job ID was provided > > in the time required) > > Again, buildsys is doing fine. It is not doing fine: A couple of minutes ago, 5 of my buildjobs failed with (Full build logs currently in http://buildsys.fedoraproject.org/build-status/failed.psp): ... # Ensuring dir /mnt/build/builder_work/f4e1eedc62933d79096a66176a549918da577753/mock-state Cleaning Root ensuring dir /var/lib/mock/fedora-development-x86_64-core-f4e1eedc62933d79096a66176a549918da577753 ensuring dir /var/lib/mock/fedora-development-x86_64-core-f4e1eedc62933d79096a66176a549918da577753/root ensuring dir /mnt/build/builder_work/f4e1eedc62933d79096a66176a549918da577753/mock-state ensuring dir /mnt/build/builder_work/f4e1eedc62933d79096a66176a549918da577753/result ensuring dir /var/lib/mock/fedora-development-x86_64-core-f4e1eedc62933d79096a66176a549918da577753 ensuring dir /var/lib/mock/fedora-development-x86_64-core-f4e1eedc62933d79096a66176a549918da577753/root ensuring dir /mnt/build/builder_work/f4e1eedc62933d79096a66176a549918da577753/mock-state ensuring dir /mnt/build/builder_work/f4e1eedc62933d79096a66176a549918da577753/result ensuring dir /var/lib/mock/fedora-development-x86_64-core-f4e1eedc62933d79096a66176a549918da577753/root/var/lib/rpm ensuring dir /var/lib/mock/fedora-development-x86_64-core-f4e1eedc62933d79096a66176a549918da577753/root/var/log ensuring dir /var/lib/mock/fedora-development-x86_64-core-f4e1eedc62933d79096a66176a549918da577753/root/dev ensuring dir /var/lib/mock/fedora-development-x86_64-core-f4e1eedc62933d79096a66176a549918da577753/root/etc/rpm ensuring dir /var/lib/mock/fedora-development-x86_64-core-f4e1eedc62933d79096a66176a549918da577753/root/tmp ensuring dir /var/lib/mock/fedora-development-x86_64-core-f4e1eedc62933d79096a66176a549918da577753/root/var/tmp ensuring dir /var/lib/mock/fedora-development-x86_64-core-f4e1eedc62933d79096a66176a549918da577753/root/etc/yum.repos.d ensuring dir /var/lib/mock/fedora-development-x86_64-core-f4e1eedc62933d79096a66176a549918da577753/root/proc ensuring dir /var/lib/mock/fedora-development-x86_64-core-f4e1eedc62933d79096a66176a549918da577753/root/dev/pts ensuring dir /var/lib/mock/fedora-development-x86_64-core-f4e1eedc62933d79096a66176a549918da577753/root/proc ensuring dir /var/lib/mock/fedora-development-x86_64-core-f4e1eedc62933d79096a66176a549918da577753/root/dev/pts /usr/sbin/mock-helper yum --installroot /var/lib/mock/fedora-development-x86_64-core-f4e1eedc62933d79096a66176a549918da577753/root groupinstall build Failed to add groups file for repository: core http://buildsys.fedoraproject.org/plague-results/fedora-development-extras/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum Trying other mirror. Error: failure: repodata/primary.xml.gz from local: [Errno 256] No more mirrors to try. unhandled node in <comps>: category unhandled node in <comps>: category unhandled node in <comps>: category unhandled node in <comps>: category unhandled node in <comps>: category Cleaning up... Done. > Please check to make sure the job did > not actually get enqueued. How about you fixing your code to not produce false alarms, if you are sure these are false alarms? > While I know that reporting this has been the rule for a while, the code > added a couple weeks ago should mean that 95% of the cases where this > error gets returned are not actually buildsys hangs. It should recover > in ~10s and continue as normal. Ralf -- fedora-extras-list mailing list fedora-extras-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-extras-list
