Re: What to do with 'make check'?

[mwoehlke]

Paul Eggert wrote:
> mwoehlke <address@hidden> writes:
> > how safe is running 'make check' as root?
>
> In practice I think it's fairly safe.  But if you're at all worried
> about it, I suggest running it under a virtual emulator.  After all,
> the whole point of 'make check' is to find bugs, and what could a
> buggy program do when run as root?

Hehe, well, since I don't have a virtual emulator (or certainly couldn't 
get one for all the systems I want to test), I think I'll skip this. I 
could probably run it on Linux but I trust others are already doing that.

> > 2. I am expecting a number of failures. How should I report these?
>
> The output of "make check" is a good start.  If a particular test fails,
> it might help to re-run that verbosely.  E.g.,
>
>    cd tests/mv
>    VERBOSE=yes make TESTS=no-target-dir check

Will do. Is it OK to bzip2 the results? Remember I expect to have 
several (as many as 10) of these!

> > to what extent will I have to chase down bugs myself (or should I
> > post results first, and go from there)?
>
> In some cases the fixes will be obvious.  In others, I'm afraid you'll
> have to fix the bugs yourself and send us patches, as we don't have
> access to your machines.
>
> > 3. How important are the local-file-system tests?
>
> That depends on how important local file systems are to applications
> running on the intended hosts.

Ok... Is there a way to tell the tests to run in something other than 
the build directory?

--
Matthew
Download. Untar. Configure. Make. Install. Lather. Rinse. Repeat.