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

Re: 'make *check' documentation Re: svn commit: r1683071 - /subversion/trunk/INSTALL

From: Branko ─îibej <brane_at_wandisco.com>
Date: Tue, 02 Jun 2015 15:19:55 +0200

On 02.06.2015 12:50, Daniel Shahaf wrote:
> danielsh_at_apache.org wrote on Tue, Jun 02, 2015 at 10:42:29 -0000:
>> +++ subversion/trunk/INSTALL Tue Jun 2 10:42:29 2015
>> @@ -590,7 +590,10 @@ II. INSTALLATION
>> $ make
>> # make install
>>
>> - You can also run the full test suite by running 'make check'.
>> + You can also run the full test suite by running 'make check'. Even
>> + in successful runs, some tests will report XFAIL; that is normal.
>> + Failed runs are indicated by FAIL or XPASS results, or a non-zero exit
>> + code from "make check".
> Shouldn't we be saying something about running one or more of
> make svnserveautocheck
> make davautocheck
> make check FS_TYPE=bdb
> make check-swig-py
> if those components are to be used?
>
> I think the last one may be covered by the bindings README, but I'm not
> sure about the others. (Context: this is the documentation for users
> building from a tarball.)

IMO, this sort of docco should be in subversin/tests/cmdline/README and
INSTALL should just point to that file.

-- Brane
Received on 2015-06-02 15:20:12 CEST

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