public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: changing the developer profile: FEATURES="test" -> FEATURES="test-fail-continue"
Date: Fri, 04 Jun 2010 17:50:24 +0200	[thread overview]
Message-ID: <4C0920C0.8020702@gentoo.org> (raw)
In-Reply-To: <AANLkTimniLRhHXnbcQuGDwHgrjkcjlVBBfStoatz2Nb6@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]

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="test" is
intended to make developers catch these failures before checking in.

However, with many packages failing tests, people started running
FEATURES="-test" or just stopped (or never used) the developer profile.
With FEATURES="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ł


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2010-06-04 15:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-04 15:11 [gentoo-dev] RFC: changing the developer profile: FEATURES="test" -> FEATURES="test-fail-continue" "Paweł Hajdan, Jr."
2010-06-04 15:35 ` Jesus Rivero (Neurogeek)
2010-06-04 15:50   ` "Paweł Hajdan, Jr." [this message]
2010-06-04 16:48 ` Jeroen Roovers
2010-06-04 17:00   ` Jeroen Roovers
2010-06-06  3:46 ` [gentoo-dev] " Ryan Hill
2010-06-07 10:10   ` Thilo Bangert
2010-06-07 12:02     ` Jeroen Roovers
2010-06-07 14:05       ` Thilo Bangert
2010-06-12  3:59       ` Ryan Hill
2010-06-07 13:53     ` "Paweł Hajdan, Jr."
2010-06-09 17:08 ` [gentoo-dev] " "Paweł Hajdan, Jr."
2010-06-10 16:28   ` Brian Harring
2010-06-10 16:36     ` Samuli Suominen
2010-06-10 17:36       ` Brian Harring

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=4C0920C0.8020702@gentoo.org \
    --to=phajdan.jr@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