[Clfs-dev] Final System Test Suites

[g.esp at free.fr]

----- Mail original -----
> De: "William Harrington" <berzerkula at cox.net>
> À: "CLFS development discussion" <clfs-dev at lists.cross-lfs.org>
> Envoyé: Mardi 23 Octobre 2012 21:50:44
> Objet: Re: [Clfs-dev] Final System Test Suites
> 
> 
> On Oct 15, 2012, at 4:47 PM, William Harrington wrote:
> 
> > Also this thread can be used for all final system test suite
> > issues.
> 
> Okay since we now have su from shadow to do the coreutils test suites,
> we still need to edit the coreutils command so the tests actually run.
> 
> Right now, using the current command:
> 
> su dummy -c "make RUN_EXPENSIVE_TESTS=yes check"
> bash: make: command not found
> 
> I was goofing around with it about amonth ago and had it run via this:
> 
> /bin/su dummy -s /tools/bin/bash -c "PATH=/tools/bin make
> RUN_EXPENSIVE_TESTS=yes check"
> 
> 
> Any input on the proper way or is that the proper way?
> 
> Sincerely,
> 
> William Harrington


I am using what LFS use
su nobody -s /bin/bash -c "PATH=$(PATH) make -k RUN_EXPENSIVE_TESTS=yes check"

-k is helpfull if you encounter an error but want to --keep-going on other tests.

For PATH=/tools/bin instead of  instead of PATH=$(PATH), I am unsure your suggest form is better.
The test suite will set his own PATH in tests/init.sh path_prepend_ to
...
PATH="$abs_path_dir_:$PATH"
...
export PATH

Will not some tests fail (or use binaries from /tools) because you did not include the path to binaries build just before coreutils?

Did you encounter the gnulib-tests/test-getlogin.c issue?
I suspect this may be related as starting the build process as non-root.
For this reason tests/mv/i-3 is skipped with '/dev/stdin is not readable' message. Using before the test chmod o+r `tty` let tests/mv/i-3test run, but didn't fix gnulib-tests/test-getlogin.c.

Gilles