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

Re: "make check" in the svn tree

From: Ben Collins-Sussman <sussman_at_newton.collab.net>
Date: 2000-09-27 18:20:40 CEST

Bob Miller <kbob@jogger-egg.com> writes:

> Currently, I can "make check" in subversion/subversion, but not in
> subversion. I want to "make check" in subversion/tools/svn2cvs, and
> it seems like it should be invoked from the top level.

`check' is a target automatically supplied by automake. However, we
don't like it, so our Makefile.am's that live in "test" subdirectories
redefine this target with our own script:

## We're overriding automake's own `check' rule, because it's extremely
## inflexible; we want better control over automated-test output.
check:
        @echo > tests.log
        @for prog in $(SVN_TESTS); do \
          echo; \
          echo -n "Running all sub-tests in $$prog..."; \
          ./$$prog >> tests.log; \
          if [ $$? -eq 0 ]; \
          then \
             echo "SUCCESS"; \
          else \
             echo; \
             echo "at least one sub-test FAILED, check tests.log:"; echo; \
             cat tests.log | grep FAIL; \
          fi; \
        done

If you want to be able to `make check' in tools/cvs2svn/, just create
a Makefile by hand. You can copy this script if you want, although it
assumes that each test program in SVN_TESTS takes args and produces
output in a certain way (as you already read in
subversion/tests-common/README).

For now, I don't see any reason to extend automake's paws into this
directory.
Received on Sat Oct 21 14:36:09 2006

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