Bruno Haible | 1 May 2008 16:53

Re: [PATCH] add tests for vc-list-files

Jim Meyering wrote:
> ... possibly get a test failure.  Such a failure doesn't
> really matter in general -- most people don't run "make syntax-check"
> or "make distcheck" -- so a test failure here is most definitely no
> cause for alarm

I routinely use "gnulib-tool --create-testdir --with-tests" as a tarball
for testing on all kinds of platforms. It contains all available modules
(except the very few ones which are known to conflict with other modules).

Therefore, in general, every test should succeed, also in the presence of
all other modules.

What are the known situations in which the vc-list-files tests will fail?

Bruno

Jim Meyering | 1 May 2008 21:10
Gravatar

Re: [PATCH] add tests for vc-list-files

Bruno Haible <bruno <at> clisp.org> wrote:
> Jim Meyering wrote:
>> ... possibly get a test failure.  Such a failure doesn't
>> really matter in general -- most people don't run "make syntax-check"
>> or "make distcheck" -- so a test failure here is most definitely no
>> cause for alarm
>
> I routinely use "gnulib-tool --create-testdir --with-tests" as a tarball
> for testing on all kinds of platforms. It contains all available modules
> (except the very few ones which are known to conflict with other modules).
>
> Therefore, in general, every test should succeed, also in the presence of
> all other modules.

Absolutely.  I tried to do that yesterday, but didn't
figure out why $(abs_top_srcdir) wasn't a parent of build-aux.
Today I've worked around that with the new abs_aux_dir variable.

> What are the known situations in which the vc-list-files tests will fail?

None.


Gmane