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

Re: Should `make check' work?

From: Karl Fogel <kfogel_at_galois.collab.net>
Date: 2000-11-02 15:22:10 CET

"make check" in the client directory is broken right now, I broke it
(knowingly, due to work in progress) a couple of days ago.

Yes, keeping "make check" working will be a goal just like "make sure
it builds", once the autobuilds are running. If someone has to commit
with a broken "make check" in some subdir, the thing to do is tweak
the "check" rule to not run the broken code until it's ready. But I
didn't do that this time, sorry. I should have it working again today.

I don't know about the ra_dav tests.

In general, people have been running "make check" in their own
subdirs, not from the top level. I guess once Matt has the autobuild
stuff running, we should be thinking of "make check" from the top
level.

-K

matt@braithwaite.net (Matthew Braithwaite) writes:
> 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

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.