FAQ

Problems with APC and/or rsync

Brian greenfield
May 31, 2009 at 3:10 pm
Hi all

Here's a list of the last 26 smoke reports sent from this FreeBSD
7.2-RELEASE box, sorted by subject:

Subject: Smoke [5.10.0] maint-5.10-1196-ga8a43ff FAIL(X) freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.10.0] maint-5.10-1196-ga8a43ff FAIL(X) freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.10.0] maint-5.10-1196-ga8a43ff PASS freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.10.0] maint-5.10-1196-ga8a43ff PASS freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.10.0] maint-5.10-1196-ga8a43ff PASS freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.10.0] maint-5.10-1196-ga8a43ff PASS freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.10.0] maint-5.10-1218-ga524575 FAIL(X) freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.10.0] maint-5.10-1218-ga524575 PASS freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.10.0] maint-5.10-1218-ga524575 PASS freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.10.0] maint-5.10-1218-ga524575 PASS freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.10.0] maint-5.10-1218-ga524575 PASS freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.10.0] maint-5.10-1218-ga524575 PASS freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.10.0] maint-5.10-1218-ga524575 PASS freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.11.0] blead-1175-gd525a7b FAIL(X) freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.11.0] blead-1175-gd525a7b FAIL(X) freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.11.0] blead-1175-gd525a7b PASS freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.11.0] blead-1175-gd525a7b PASS freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.11.0] blead-1175-gd525a7b PASS freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.11.0] blead-1175-gd525a7b PASS freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.11.0] blead-1211-gbd67d4d FAIL(X) freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.11.0] blead-1211-gbd67d4d PASS freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.11.0] blead-1213-gb8de32d PASS freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.11.0] blead-1213-gb8de32d PASS freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.11.0] blead-1213-gb8de32d PASS freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.11.0] blead-1214-gec6d81a PASS freebsd 7.2-RELEASE (amd64/1 cpu)
Subject: Smoke [5.11.0] blead-1221-gcddedc1 PASS freebsd 7.2-RELEASE (amd64/1 cpu)

As you can see, I've been smoking the same builds over and over
again. This *isn't* intentional. After poking around, I've discovered
that between APC and rsync, I'm being sent the same builds. Here's
what happened from 5 consecutive rsyncs:

bri@bsd:~/smoke/tmp$ /usr/local/bin/rsync -az --delete public.activestate.com::perl-5.10.x . ; cat .patch
maint-5.10 2009-05-27.00:14:05 a524575ae930f79c9d69eb19db19ad24b558b4f0 GitLive-maint-5.10-1218-ga524575
bri@bsd:~/smoke/tmp$ /usr/local/bin/rsync -az --delete public.activestate.com::perl-5.10.x . ; cat .patch
maint-5.10 2009-05-20.22:19:05 a8a43ff0f2638c954fe34867dadcb2d38093888d GitLive-maint-5.10-1196-ga8a43ff
bri@bsd:~/smoke/tmp$ /usr/local/bin/rsync -az --delete public.activestate.com::perl-5.10.x . ; cat .patch
maint-5.10 2009-05-27.00:14:05 a524575ae930f79c9d69eb19db19ad24b558b4f0 GitLive-maint-5.10-1218-ga524575
bri@bsd:~/smoke/tmp$ /usr/local/bin/rsync -az --delete public.activestate.com::perl-5.10.x . ; cat .patch
maint-5.10 2009-05-27.00:14:05 a524575ae930f79c9d69eb19db19ad24b558b4f0 GitLive-maint-5.10-1218-ga524575
bri@bsd:~/smoke/tmp$ /usr/local/bin/rsync -az --delete public.activestate.com::perl-5.10.x . ; cat .patch
maint-5.10 2009-05-20.22:19:05 a8a43ff0f2638c954fe34867dadcb2d38093888d GitLive-maint-5.10-1196-ga8a43ff

I've updated my rsync to the latest in the Ports collection (from
2.9.6?) and the same happened:

bri@bsd:~/smoke/tmp$ /usr/local/bin/rsync --version
rsync version 3.0.6 protocol version 30
Copyright (C) 1996-2009 by Andrew Tridgell, Wayne Davison, and others.
Web site: http://rsync.samba.org/
Capabilities:
64-bit files, 32-bit inums, 64-bit timestamps, 64-bit long ints,
socketpairs, hardlinks, symlinks, IPv6, batchfiles, inplace,
append, ACLs, xattrs, no iconv, symtimes

rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you
are welcome to redistribute it under certain conditions. See the GNU
General Public Licence for details.

I've also tried this on a Debian/testing box and the same happens. Can
anyone give me a clue as to what's happening and how to put it right?
reply

Search Discussions

1 response

  • Brian greenfield at May 31, 2009 at 4:35 pm

    On Sun, May 31, 2009 at 04:10:13PM +0100, brian greenfield wrote:

    bri@bsd:~/smoke/tmp$ /usr/local/bin/rsync -az --delete public.activestate.com::perl-5.10.x . ; cat .patch
    gah.

    Changing the rsync address to perl5.git.perl.org::perl-5.10.x avoids
    the problem.

Related Discussions

Discussion Navigation
viewthread | post

1 user in discussion

Brian greenfield: 2 posts