Re: [gentoo-dev] Make FEATURES=test the default

[Danny van Dyk]

Am Samstag, 5. August 2006 11:19 schrieb Kevin F. Quinn:
> On Sat, 5 Aug 2006 02:39:16 +0200
>
> Danny van Dyk <kugelfang@g.o> wrote:
> > Am Samstag, 5. August 2006 02:11 schrieb Kevin F. Quinn:
> > > At the very least, ebuild maintainers and ATs should be running
> > > with tests switched on.  If the tests are known to fail then the
> > > ebuild can either RESTRICT=test, or just return successfully from
> > > src_test() where the test report is useful even if some tests
> > > fail.
> > >
> > > Thoughts?
> >
> > * autoconf takes ages (longer than compiling glibc here).
> > * glibc tests fail on amd64 since at least a year.
> > * automake|e2fsprogs|neon|gettext|tar have failed tests for me more
> > than once.
> >
> > As soon as these are fixed, i wouldn't mind making FEATURES="test"
> > a default.
>
> Well, if something fails its tests but you still want it regardless
> or you want to skip the test phase for some other reason, you can
> always do FEATURES="-test" emerge <foo>.
>
> Changing the default doesn't prevent people from skipping tests,
> however in the long term it will reduce the amount of stuff committed
> to the tree that doesn't pass tests.  It will increase the amount of
> times a system or world update falls over, but changing the default
> will raise the priority for getting these things fixed.
>
> There are many packages in the tree for which it is clear the
> maintainer did not even attempt to run the tests - e.g.
> https://bugs.gentoo.org/show_bug.cgi?id=139414  To my mind committing
> packages without even bothering to try the test phase is inexcusable.

Something?

Please re-read the list of packages that fail tests:
 * glibc
 * autoconf
 * gettext
 * tar
That makes _4_ system packages. Before I would consider making 
FEATURES=test a default, I would add least want the system set to 
actually merge with it.

Danny
-- 
Danny van Dyk <kugelfang@g.o>
Gentoo/AMD64 Project, Gentoo Scientific Project
-- 
gentoo-dev@g.o mailing list