[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é: Lundi 15 Octobre 2012 22:44:19
> Objet: [Clfs-dev] Final System Test Suites
> 
> Hello CLFS community,
> 
> We have an issue that needs to be addressed.
> 
> Util-linux used to provide su, which we used when testing coreutils.
> 
> We've always installed and used shadow's su, and shadow is installed
> after coreutils, and we can't use that su as of right now, unless we
> test coreutils after installing shadow.
> 
> I was thinking, maybe when building coreutils, add to the instructions
> to extract shadow's su src file and build it to use for the test suite
> phase of coreutils.  I haven' t tested this, and I'm coming up with
> ideas on a whim.
> 
> We can move shadow before coreutils. I'm not sure how much of the
> final system it needs before being built. I think one time I did build
> shadow before coreutils and didn't see anyting weird, but really all
> we need is su at that point.
> 
> Any input is greatly appreciated.
> 
I have tried building before coreutils on my build system and coreutils tests simply work (with added PATH=$PATH).
I even now build before util-linux because this allow me to run the non-root part of util-linux tests using something similar to coreutils like:
su nobody -s /bin/bash -c "PATH=$(PATH) make check"

I send a patch to skip util-linux tests using bc and that was accepted today. So it should be possible in the futur to run a vanilia util-linux non-root tests without FAILED.

That would be hard to run util-linux root tests. First the test suite is not ready to run in everyone machine due to hardcoded /dev/loopx value. Secondly, modprobe and scsi_debug module from running kernel are needed for many tests.

I checked shadow build from log and didn't see any difference when building before coreutils vs before util-linux.

Gilles