From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1OKZAc-0007LK-3V for garchives@archives.gentoo.org; Fri, 04 Jun 2010 15:50:54 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 36DEEE0C32; Fri, 4 Jun 2010 15:50:51 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 4D542E0C0F for ; Fri, 4 Jun 2010 15:50:38 +0000 (UTC) Received: from [192.168.1.109] (aatl140.neoplus.adsl.tpnet.pl [83.5.249.140]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id C03801B4041 for ; Fri, 4 Jun 2010 15:50:33 +0000 (UTC) Message-ID: <4C0920C0.8020702@gentoo.org> Date: Fri, 04 Jun 2010 17:50:24 +0200 From: =?UTF-8?B?IlBhd2XFgiBIYWpkYW4sIEpyLiI=?= User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] RFC: changing the developer profile: FEATURES="test" -> FEATURES="test-fail-continue" References: <4C0917B1.8080307@gentoo.org> In-Reply-To: X-Enigmail-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigFB0B9ED600E0D4DB17911F7B" X-Archives-Salt: 40c02f3b-911d-4a25-85a1-6660556aa565 X-Archives-Hash: b80978d6c18a2603bb6ed53b37fb2075 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigFB0B9ED600E0D4DB17911F7B Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 6/4/10 5:35 PM, Jesus Rivero (Neurogeek) wrote: > I've been thinking about this for a while. Some packages have tests > that are meant only for upstream in certain conditions > and are not meant to be ran during installing. I think that in extreme cases src_test should not call such tests. > As we have ARCH teams, > couldn't we think a way in which TEST teams can > be created? I mean, a bunch of devs only focused on making tests work > or just restrict them? I don't think that would be effective. Making the tests work is hard, especially for packages like gcc, or python. Having FEATURES=3D"test" is intended to make developers catch these failures before checking in. However, with many packages failing tests, people started running FEATURES=3D"-test" or just stopped (or never used) the developer profile.= With FEATURES=3D"test test-fail-continue" we should get best of both worlds: run tests always, but don't frustrate people by making build fail "in the middle of long emerge". Pawe=C5=82 --------------enigFB0B9ED600E0D4DB17911F7B Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (Darwin) iEYEARECAAYFAkwJIMQACgkQuUQtlDBCeQK9eACfUI7deedH1XyP5hRkw5YKuEuc 7j4AoIYQSJ8Spqw52XOQJq087lk/kwhv =z7p3 -----END PGP SIGNATURE----- --------------enigFB0B9ED600E0D4DB17911F7B--