[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 1.7.1 up for testing / signing

From: Stefan Sperling <stsp_at_elego.de>
Date: Sun, 18 Dec 2011 12:17:18 +0100

On Sun, Dec 18, 2011 at 02:35:39AM -0800, rupert.thurner wrote:
> On Oct 21, 9:51 am, Stefan Sperling <s..._at_elego.de> wrote:
> > On Thu, Oct 20, 2011 at 04:19:08PM -0700, rupert.thurner wrote:
> > > on solaris, one test is failing for 1.7.0 ...
> > > At least one test FAILED, checking /home/rupert/mgar-sav/pkg/
> > > subversion/trunk/work/solaris9-sparc/build-isa-sparcv8/
> > > subversion-1.7.0/tests.log
> > > FAIL:  copy_tests.py 86:changeddiraftercommitshouldmatch
> > >checkout
> > > Summary of test results:
> > >   1552 tests PASSED
> > >   42 tests SKIPPED
> > >   23 tests XFAILED (1 WORK-IN-PROGRESS)
> > >   1 test FAILED
> > > gmake: *** [check] Error 1
> >
> > Please show the output of:
> >
> > $ cd /home/rupert/mgar-sav/pkg/subversion/trunk/work/solaris9-sparc/build-isa-sp arcv8/subversion-1.7.0/subversion/tests/cmdline
> > $ ./copy_tests.py 86 --verbose
>
>
> rupert @ unstable9s : ~/mgar-sav/pkg/subversion/trunk/work/solaris9-
> sparc/build-isa-sparcv8/subversion-1.7.2/subversion/tests/cmdline
> $ ./copy_tests.py 86 --verbose

> PASS: copy_tests.py 86: changed dir after commit should match
> checkout

So this time, it passed. This is probably just a race condition in the
test where it might not succeed if timestamps on disk aren't updated
quickly enough. Can you get it to fail again by running it a couple
of times?

I think you can safely ignore this failure.
Received on 2011-12-18 12:17:55 CET

This is an archived mail posted to the Subversion Dev mailing list.