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

RE: svn commit: r1493097 - /subversion/trunk/subversion/tests/cmdline/svntest/main.py

From: Bert Huijben <bert_at_qqmail.nl>
Date: Wed, 19 Jun 2013 14:01:57 +0200

> -----Original Message-----
> From: Ivan Zhakov [mailto:ivan_at_visualsvn.com]
> Sent: woensdag 19 juni 2013 13:50
> To: dev_at_subversion.apache.org; Stefan Sperling
> Subject: Re: svn commit: r1493097 -
> /subversion/trunk/subversion/tests/cmdline/svntest/main.py
>
> On Fri, Jun 14, 2013 at 6:40 PM, <stsp_at_apache.org> wrote:
> > Author: stsp
> > Date: Fri Jun 14 14:40:17 2013
> > New Revision: 1493097
> >
> > URL: http://svn.apache.org/r1493097
> > Log:
> > Run tests with an exclusive lock on working copies. This should reduce test
> > run time and also ensures that exclusive locking mode is tested.
> >
> > I've run ra_local and ra_serf tests with this change and got no failures.
> > In any case, if there were any test failures with exlusive locking mode
> > enabled, they'd most likely expose bugs in the test suite or Subversion
> itself.
> >
> I don't like this change actually:
> 1. Running tests in different configuration than regular users are
> using bad practice
> 2. It also seems to broke svn benchmarks posted every week, because
> now we get totally different numbers for operations.
>
> Could you please make option to running test suite with exclusive
> locking mode and leave it 'off' by default. Thanks!

+1

        Bert
Received on 2013-06-19 14:03:04 CEST

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