From: "Jesus Rivero (Neurogeek)" <neurogeek@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, 4 Jun 2010 11:05:43 -0430 [thread overview]
Message-ID: <AANLkTimniLRhHXnbcQuGDwHgrjkcjlVBBfStoatz2Nb6@mail.gmail.com> (raw)
In-Reply-To: <4C0917B1.8080307@gentoo.org>
Hi,
On Fri, Jun 4, 2010 at 10:41 AM, "Paweł Hajdan, Jr."
<phajdan.jr@gentoo.org> wrote:
> What do you think about doing the following change in
> /usr/portage/profiles/targets/developer/make.defaults:
>
> replace "test" with "test-fail-continue" to make it just less
> frustrating (we still have a lot of test failures)
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. 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?
This team (or a Gentoo project) can work hand by hand with other teams
and ARCH members.
Is it even possible?
>
> Hopefully that will also make more of us use the developer profile, and
> detect test failures.
>
> What do you think?
>
> Paweł
Best regards,
--
Jesus Rivero (Neurogeek)
next prev parent reply other threads:[~2010-06-04 15:36 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) [this message]
2010-06-04 15:50 ` "Paweł Hajdan, Jr."
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=AANLkTimniLRhHXnbcQuGDwHgrjkcjlVBBfStoatz2Nb6@mail.gmail.com \
--to=neurogeek@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