From: Kent Fredric <kentfredric@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Handling of tests (was: GCC USE flag changes)
Date: Thu, 2 May 2013 13:24:07 +1200 [thread overview]
Message-ID: <CAATnKFCR=Y5jeTF02LiDJKicKg8x02maMWPxvvdWaxs0gKbygQ@mail.gmail.com> (raw)
In-Reply-To: <20130501191852.75fadabc@caribou.gateway.2wire.net>
[-- Attachment #1: Type: text/plain, Size: 2002 bytes --]
2 other classes of tests you may want to consider :
- network/internet accessibility required tests
- markers for tests that are known/expected to fail under many conditions
and are not worth end-user-testing, but end-users can force-running any way
if they really want to see the individual failures.
On 2 May 2013 13:18, Ryan Hill <dirtyepic@gentoo.org> wrote:
> On Wed, 1 May 2013 10:14:02 +0200
> Ralph Sennhauser <sera@gentoo.org> wrote:
>
> > On Tue, 30 Apr 2013 21:25:40 -0600
> > Ryan Hill <dirtyepic@gentoo.org> wrote:
> >
> > > I'm also going to rename the "test" flag to "regression-test" or
> > > something similar to get it out of FEATURES="test" control. The
> > > testsuite is a huge time-suck and only useful to developers IMO
> > > (always expected to fail and primarily meant to be used to check for
> > > regressions between patchsets). I'm a big supporter of
> > > FEATURES="test" by default and I think this is a small step towards
> > > that.
> >
> > This step is so tiny that we wont ever reach the goal like this.
>
> I was hoping it would set a precedent and then people would start thinking
> of
> splitting up test into categories, maybe even start a thread about it ;).
>
> > Let's
> > start to properly classify test into categories, like for instance
> >
> > - expected to be run (cheap, no silly deps)
> > - good thing if run (still reasonable wrt resources) (current src_test)
> > - if you are the maintainer or simply curious. (boost, jtreg and
> > friends)
>
> Something like "dev-test" or "qa-test"? I can think of a couple packages..
>
> > ... and improve on how to configure Portage whether to run tests of any
> > given category.
>
> Yeah I'd love to be able to do something like emerge TESTS="dev qa
> system -extradeps -expensive" @world.
>
>
> --
> gcc-porting
> toolchain, wxwidgets
> @ gentoo.org
>
--
Kent
perl -e "print substr( \"edrgmaM SPA NOcomil.ic\\@tfrken\", \$_ * 3, 3 )
for ( 9,8,0,7,1,6,5,4,3,2 );"
http://kent-fredric.fox.geek.nz
[-- Attachment #2: Type: text/html, Size: 3017 bytes --]
next prev parent reply other threads:[~2013-05-02 1:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 3:25 [gentoo-dev] GCC USE flag changes Ryan Hill
2013-05-01 3:33 ` Patrick Lauer
2013-05-01 3:49 ` [gentoo-dev] " Ryan Hill
2013-05-01 5:29 ` Rick "Zero_Chaos" Farina
2013-05-01 7:00 ` Diego Elio Pettenò
2013-05-02 0:59 ` Ryan Hill
2013-05-02 1:30 ` Matt Turner
2013-05-02 4:57 ` Rick "Zero_Chaos" Farina
2013-05-02 5:09 ` Hans de Graaff
2013-05-01 8:19 ` Ralph Sennhauser
2013-05-01 8:14 ` [gentoo-dev] Handling of tests (was: GCC USE flag changes) Ralph Sennhauser
2013-05-02 1:18 ` [gentoo-dev] " Ryan Hill
2013-05-02 1:24 ` Kent Fredric [this message]
2013-05-02 4:21 ` Mike Frysinger
2013-05-02 4:36 ` Kent Fredric
2013-05-02 5:06 ` [gentoo-dev] Re: Handling of tests Rick "Zero_Chaos" Farina
2013-05-10 7:57 ` [gentoo-dev] Re: Handling of tests (was: GCC USE flag changes) Ralph Sennhauser
2013-05-01 19:47 ` [gentoo-dev] GCC USE flag changes "Paweł Hajdan, Jr."
2013-05-15 1:07 ` [gentoo-dev] " Ryan Hill
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='CAATnKFCR=Y5jeTF02LiDJKicKg8x02maMWPxvvdWaxs0gKbygQ@mail.gmail.com' \
--to=kentfredric@gmail.com \
--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