From: Thilo Bangert <bangert@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: RFC: changing the developer profile: FEATURES="test" -> FEATURES="test-fail-continue"
Date: Mon, 7 Jun 2010 12:10:04 +0200 [thread overview]
Message-ID: <201006071210.07109.bangert@gentoo.org> (raw)
In-Reply-To: <20100605214634.26fa6b78@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 2119 bytes --]
Ryan Hill <dirtyepic@gentoo.org> said:
> On Fri, 04 Jun 2010 17:11:45 +0200
>
> "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)
> >
> > Hopefully that will also make more of us use the developer profile,
> > and detect test failures.
> >
> > What do you think?
>
> I would say it's an improvement only because it might prevent one or
> two people from completely disabling it first chance they get. :)
>
> IMO, test failures should be given the same status as build failures.
> Packages shouldn't be commited until they're fixed or bypassed.
> Following that reasoning, FEATURES="test" is the correct setting for
> the dev profile. It _should_ be annoying when you hit it, that's the
> point. Fix it! What's the point of even having a test suite if it
> always fails? You'd be better off to RESTRICT it and save yourself
> some bug reports from me and all the other users you're foisting build
> errors on.
>
> But in the real world it seems it's just never going to happen. I've
> been arguing this for years but people simply don't care. It doesn't
> help that we don't have any finer control than "on" or "off". I'd
> like to be able to say things like "these tests should only be run by
> developers" or "some failures are normal" or "hope you have 10 hours
> to run this" or "don't run these as root" or "don't run tests on arm"
> etc etc. I'd like a pony while I'm at it.
>
> Sorry about the rant. This is one of my biggest long-standing
> annoyances.
>
> Um, so yeah. For it!
as it seems, there is disagreement about the issue among developers.
Perhaps the council would like to settle this, so that we can go on with
our lives.
i do agree, that all packages should build successfully including the test
phase. RESTRICTing the test and an open bug when this is not the case.
thanks
Thilo
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-06-07 10:10 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."
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 [this message]
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=201006071210.07109.bangert@gentoo.org \
--to=bangert@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