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

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

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Tue, 2 Jun 2015 10:50:23 +0000

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.)
Received on 2015-06-02 12:50:31 CEST

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