Several previous postings have indicated that people have been able to
run `make check' -- for example Branko's postings about builds on
various platforms, and Karl's Milestone 1 posting. I have not had
such luck.
I wanted to incorporate `make check' into the automatic builds, but
since it gave me some problems (starting from a clean checkout and
build), I thought it'd be worthwhile to ask whether it's *supposed* to
work, and whether spamming dev or individual developers when the tests
fail is desirable at this time.
The two tests that failed were:
gmake[2]: Entering directory `/usr/home/mab/subversion-stage/subversion/subversion/libsvn_ra_dav/tests'
Running all sub-tests in ra-dav-test...usage: ./ra-dav-test REPOSITORY_URL TARGET_DIR
at least one sub-test FAILED, check tests.log:
gmake[2]: *** [check] Error 1
and
gmake[2]: Entering directory `/usr/home/mab/subversion-stage/subversion/subversion/client/tests'
sh ./svn-test.sh
Checking out t1.
A t1/iota
A t1/A
A t1/A/mu
A t1/A/B
A t1/A/B/lambda
A t1/A/B/E
A t1/A/B/E/alpha
A t1/A/B/E/beta
A t1/A/B/F
A t1/A/C
A t1/A/D
A t1/A/D/gamma
A t1/A/D/G
A t1/A/D/G/pi
A t1/A/D/G/rho
A t1/A/D/G/tau
A t1/A/D/H
A t1/A/D/H/chi
A t1/A/D/H/psi
A t1/A/D/H/omega
Modifying t1/A/D/G/pi.
Modifying t1/A/mu.
Adding t1/newfile1.
This is added file newfile1.
Adding t1/A/B/E/newfile2.
This is added file newfile2.
Deleting versioned file A/D/H/omega, with --force.
apr_error: #2, src_err 0, canonical err 2 : No such file or directory
svn_client_delete: error deleting t1/A/D/H/omega
Committing changes in t1.
apr_error: #2, src_err 0, canonical err 2 : No such file or directory
contents_identical_p: apr_open failed on `./A/B/lambda'
Updating t2 from changes in t1.
svn_error: #21008 no element found at line 15
gmake[2]: Leaving directory `/usr/home/mab/subversion-stage/subversion/subversion/client/tests'
Received on Sat Oct 21 14:36:14 2006