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

Re: Log-addressing branch ready for review

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Sat, 30 Nov 2013 15:23:19 +0200

Daniel Shahaf wrote on Sat, Nov 30, 2013 at 15:19:56 +0200:
> Stefan Fuhrmann wrote on Sat, Nov 30, 2013 at 08:48:30 +0100:
> > Again, you are missing the point. You are saying that there
> > are lots of possible configurations and various combinations.
> > I'm saying that we *are* actually able to test many variants.
> > One simply needs to update their overall test script.
>
> There are classes of problems that our test suite simply isn't designed
> to catch.
>
> For example:
>
> - We won't catch 'premature kill -9' bugs (r1494298)
> - We won't catch concurrency bugs (r1302613)

As another example, we have architectue-dependent code, for example
the definition of SVN_UNALIGNED_ACCESS_IS_OK. In those cases, do we
test the "unlikely" branch (eg: SVN_UNALIGNED_ACCESS_IS_OK=0) too?

My build script defines -DSVN_UNALIGNED_ACCESS_IS_OK=0 for precisely
this reason.
Received on 2013-11-30 14:23:56 CET

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