Thanks!.
With regards
Kamesh Jayachandran
-----Original Message-----
From: Lieven Govaerts [mailto:lieven.govaerts_at_gmail.com]
Sent: Mon 4/14/2008 5:42 PM
To: Kamesh Jayachandran
Cc: dev_at_subversion.tigris.org
Subject: Re: 1.5.0-rc3 up for signing/testing
Ok, this is just an output ordering issue.
This is a consequence of issue #2932: as ra_serf uses multiple
connections to dispatch and receive file diffs, the order in which the
changes are shown can be out of order. In the test suite we only see
this from time to time as there's only a limited number of files
involved, so changes are typically received in order.
Nothing to worry about, for now.
Lieven
On Mon, Apr 14, 2008 at 1:58 PM, Kamesh Jayachandran <kamesh_at_collab.net> wrote:
>
>
>
> Lieven,
>
> Find the tests.log showing the failure.
>
>
> With regards
> Kamesh Jayachandran
> -----Original Message-----
>
> From: Lieven Govaerts [mailto:lieven.govaerts_at_gmail.com]
> Sent: Mon 4/14/2008 1:33 PM
> To: Kamesh Jayachandran
> Cc: dev_at_subversion.tigris.org
> Subject: Re: 1.5.0-rc3 up for signing/testing
>
> Kamesh,
>
> can you send me the output of merge test 4 over ra_serf? Update test
> 41 is fixed, but the merge test issue doesn't happen on the buildbot.
>
> thx, Lieven
>
> On Sun, Apr 13, 2008 at 7:39 PM, Kamesh Jayachandran <kamesh_at_collab.net>
> wrote:
> >
> >
> >
> > Hi All,
> >
> > +1 to release.
> >
> > Following are my observation when I tested
> >
> http://orac.ece.utexas.edu/pub/svn/1.5.0-rc3/bastrop-pine/subversion-1.5.0-rc3.tar.bz2
> >
> >
> > make check [fsfs, bdb] - All tests pass.
> > make svnserveautocheck [fsfs, bdb] - All tests pass, but tests took
> > longggggg time to complete.
> > This svnserve test alone took 5+ hours in my box. FYI, I used to see
> this
> > behaviour some
> > time in the past but things started working fast after that. I observed
> > this slowness in RC2.
> > May be it could be my new system issue(I did not see this vague slowness
> in
> > RC1 testing from my office
> > laptop).
> >
> >
> > make davautocheck [fsfs, bdb] * [neon] - All tests pass.
> >
> > make davautocheck [fsfs, bdb] * [serf] - All tests pass except
> > update_tests-41 and merge_tests-4.
> >
> > My new signature(from my home)
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.6 (GNU/Linux)
> >
> > iD8DBQBIAoy55YUrqC3H2YoRAtezAJ9Y1FDyu3TMC3vFKuF+wf1zbLltOACfZRzC
> > O2Imi8tjCjPeIvkq0muJQbA=
> > =RmMS
> > -----END PGP SIGNATURE-----
> >
> >
> > With regards
> > Kamesh Jayachandran
> >
> >
> > -----Original Message-----
> > From: Hyrum K. Wright [mailto:hyrum_wright_at_mail.utexas.edu]
> > Sent: Sat 4/12/2008 9:50 PM
> > To: dev_at_subversion.tigris.org
> > Subject: 1.5.0-rc3 up for signing/testing
> >
> > Hoping that the third time is the charm, I'm pleased to announce that
> > Subversion 1.5.0-rc3 is up for testing and signing. The magic revision
> > is r30562.
> >
> > http://orac.ece.utexas.edu/pub/svn/1.5.0-rc3/
> >
> > As usual, signatures from full committers back to me, and enthusiastic
> > tester feedback is welcome. At this point, this candidate is not yet
> > blessed for wide release, so please don't make it available to people
> > not interested in test-driving the new release.
> >
> > Distro package maintainers, please do NOT include any pre-release
> > builds, even blessed, into operating system distros. The reasons for
> > not doing so were very eloquently outlined by Karl in a mail, which is
> > summarized at the above address.
> >
> > The quick version is: we don't guarantee compatibility between the
> > pre-releases and the final release, so if people install the release
> > candidate, all their repositories and working copies might break
> > unrepairably when they upgrade to 1.5.0 proper. We don't want that kind
> > of bad publicity, and neither do you.
> >
> > Happy testing!
> >
> > -Hyrum
> >
> >
> >
>
>
>
Received on 2008-04-14 14:41:00 CEST