From: Jakub Moc <jakub@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Make FEATURES=test the default
Date: Sat, 05 Aug 2006 02:26:16 +0200 [thread overview]
Message-ID: <44D3E5A8.8010107@gentoo.org> (raw)
In-Reply-To: <20060805021158.11ca6b15@c1358217.kevquinn.com>
[-- Attachment #1: Type: text/plain, Size: 1397 bytes --]
Kevin F. Quinn wrote:
> I'd like to suggest we make FEATURES=test (and therefore USE=test) the
> default behaviour, rather than the opt-in we currently have. Far too
> many packages fail their test phase.
Sure everyone likes to watch glibc failing? :P </joke>
Well, can't be done until bugs such as
http://bugs.gentoo.org/show_bug.cgi?id=69343 are solved (at least as in
sticking RESTRICT=test there) instead of being ignored.
> 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.
See above. And even then, I don't think it's a good idea to force this
upon users. Lots of packages have tests that are very time-consuming,
and there are packages that always fail tests and it's pretty much
expected (PHP is one of them; and while the failure isn't fatal there,
it still takes tons of time to go thru those ~2000 tests). And there are
tons of packages where tests are more or less unmaintained.
--
Best regards,
Jakub Moc
mailto:jakub@gentoo.org
GPG signature:
http://subkeys.pgp.net:11371/pks/lookup?op=get&search=0xCEBA3D9E
Primary key fingerprint: D2D7 933C 9BA1 C95B 2C95 B30F 8717 D5FD CEBA 3D9E
... still no signature ;)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-08-05 0:32 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-05 0:11 [gentoo-dev] Make FEATURES=test the default Kevin F. Quinn
2006-08-05 0:18 ` Ciaran McCreesh
2006-08-05 0:18 ` Alec Warner
2006-08-05 9:05 ` Kevin F. Quinn
2006-08-06 11:23 ` Paul de Vrieze
2006-08-05 0:25 ` Joshua Jackson
2006-08-05 9:33 ` Kevin F. Quinn
2006-08-05 11:14 ` Sascha Geschwandtner
2006-08-05 11:58 ` Marius Mauch
2006-08-05 12:21 ` Sascha Geschwandtner
2006-08-05 12:36 ` Sascha Geschwandtner
2006-08-05 13:29 ` Stephen P. Becker
2006-08-05 15:23 ` Marius Mauch
2006-08-05 18:31 ` Mike Frysinger
2006-08-05 18:56 ` Stephen P. Becker
2006-08-05 19:34 ` Mike Frysinger
2006-08-05 20:07 ` Stephen P. Becker
2006-08-05 20:13 ` Mike Frysinger
2006-08-05 20:20 ` Ned Ludd
2006-08-05 11:15 ` Matthias Schwarzott
2006-08-05 13:50 ` [gentoo-dev] " Duncan
2006-08-05 13:50 ` Duncan
2006-08-05 0:26 ` Jakub Moc [this message]
2006-08-05 16:07 ` [gentoo-dev] " Tim Yamin
2006-08-06 12:31 ` Paul de Vrieze
2006-08-05 0:39 ` Danny van Dyk
2006-08-05 9:19 ` Kevin F. Quinn
2006-08-05 9:49 ` Danny van Dyk
2006-08-05 10:57 ` Kevin F. Quinn
2006-08-05 13:21 ` Ned Ludd
2006-08-05 18:35 ` Mike Frysinger
2006-08-05 18:48 ` Harald van Dijk
2006-08-05 19:35 ` Mike Frysinger
2006-08-05 19:25 ` Kevin F. Quinn
2006-08-05 15:14 ` [gentoo-dev] " Sven Köhler
2006-08-05 15:31 ` Markus Rothe
2006-08-05 15:35 ` Kevin F. Quinn
2006-08-05 15:48 ` Ciaran McCreesh
2006-08-05 16:04 ` Alec Warner
2006-08-05 17:49 ` Harald van Dijk
2006-08-18 22:03 ` [gentoo-dev] " Hanno Böck
2006-08-19 0:00 ` [gentoo-dev] " Christian 'Opfer' Faulhammer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44D3E5A8.8010107@gentoo.org \
--to=jakub@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox