From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1G9A47-0002ic-7o for garchives@archives.gentoo.org; Sat, 05 Aug 2006 00:30:55 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.7/8.13.6) with SMTP id k750Sh0s010745; Sat, 5 Aug 2006 00:28:43 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by robin.gentoo.org (8.13.7/8.13.6) with ESMTP id k750PJtr027829 for ; Sat, 5 Aug 2006 00:25:20 GMT Received: from [10.99.0.1] (adsl-71-158-135-138.dsl.renocs.sbcglobal.net [71.158.135.138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 4C59164A9F for ; Sat, 5 Aug 2006 00:25:19 +0000 (UTC) Message-ID: <44D3E56D.9040205@gentoo.org> Date: Fri, 04 Aug 2006 17:25:17 -0700 From: Joshua Jackson User-Agent: Thunderbird 1.5.0.5 (X11/20060804) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Make FEATURES=test the default References: <20060805021158.11ca6b15@c1358217.kevquinn.com> In-Reply-To: <20060805021158.11ca6b15@c1358217.kevquinn.com> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 60987033-7ba5-42d5-a2fb-0ee4958b7a56 X-Archives-Hash: d84a96a5cfaef3a31ef8ad6f2c22afb0 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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. > > Since we encourage users to set CFLAGS in ways that upstream may not > have predicted, if upstream go to the trouble of providing tests it > seems sensible to me that they should be run, unless there is a very > good reason not to run them. This will help pick up faults that are due > to the compiler version, CFLAGS etc much more consistently. > > 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? I can say from experience that there are a great heaping load of packages currently that fail their test suite, the sci-team seems to be the best in this regard for passing the tests successfully. If we do in fact plan on making this the default, we should be prepared for a increase in bugs from users who will now have ebuilds stop on failed test suites. While I agree that it would be nice to see more people using test and collision-protect I don't think its something we should enable at this point in time till we have many packages working correctly with the feature. If however people feel that by enabling it, that it'll make us actually fix these issues then I'd like to see it move forward. I'm just curious as to why this has come up suddenly Kevin? p.s I hope all dev's run with test and collision-protect, I know I know you don't but I can hope. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE0+VtSENan+PfizARAhNtAKCclIg8ikGcaTgQ9E5YPBjPj93IlACeJyNX ER9yFoXQ3hOKzoMq4OxL3Rg= =uS4D -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list