public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Piotr Jaroszyński" <peper@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] tests
Date: Tue, 1 May 2007 15:08:56 +0200	[thread overview]
Message-ID: <200705011508.57220.peper@gentoo.org> (raw)

Hello,

There was some discussion about forcing/not forcing tests in EAPI-1, but there 
was clearly no compromise. Imho, tests are very important and thus I want to 
discuss them a little more, but in more sensible fashion.

Firstly each test can be(not all categories are mutually exclusive):
- not existant
- non-functional
- not runnable from ebuild
- useful but unreasonable resource-wise
- useful and reasonable resource-wise
- necessary
- known to partially fail but with a way of skipping failing tests
- known to partially fail but with no easy way of skipping failing tests
Is that list comprehensive?

Secondly we must answer the question how precisely we want to distinguish 
them, so users/dev can choose which categories of tests they want to run. 
What comes to mind is:
- run all tests
- run only necessary tests
- run only reasonable tests
- don't run tests at all
Again, is that list comprehensive?

Please don't post solutions unless we figure out which options we really want 
to deliver.

-- 
Best Regards,
Piotr Jaroszyński
--
gentoo-dev@gentoo.org mailing list



             reply	other threads:[~2007-05-01 13:14 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 13:08 Piotr Jaroszyński [this message]
2007-05-01 13:24 ` [gentoo-dev] tests Josh Sled
2007-05-01 13:32   ` Ciaran McCreesh
2007-05-01 15:50 ` Alec Warner
2007-05-01 16:04 ` Daniel Gryniewicz
2007-05-01 16:23   ` Vlastimil Babka
2007-05-01 17:18 ` Maurice van der Pot
2007-05-01 17:35   ` Ciaran McCreesh
2007-05-01 19:53     ` Maurice van der Pot
2007-05-01 20:05       ` Piotr Jaroszyński
2007-05-02  5:58         ` Rémi Cardona
2007-05-02  6:53           ` Danny van Dyk
2007-05-01 21:52       ` Josh Saddler
2007-05-01 22:31         ` Stephen Bennett
2007-05-01 22:28           ` Josh Saddler
2007-05-01 22:47             ` Piotr Jaroszyński
2007-05-01 23:08         ` Ciaran McCreesh
2007-05-01 23:06       ` Ciaran McCreesh
2007-05-01 17:58   ` Piotr Jaroszyński
2007-05-01 19:24 ` Rémi Cardona
2007-05-01 20:10   ` Jure Varlec
2007-05-01 22:06     ` Robin H. Johnson
2007-05-01 20:25 ` [gentoo-dev] tests Piotr Jaroszyński
2007-05-01 23:32 ` [gentoo-dev] tests Marius Mauch
2007-05-01 23:46   ` Daniel Gryniewicz
2007-05-01 23:55     ` Ciaran McCreesh
2007-05-02  0:34       ` Brian Harring
2007-05-02 11:52         ` Ciaran McCreesh
2007-05-02  0:08     ` Robin H. Johnson
2007-05-02  0:12     ` Stephen Bennett
2007-05-02  1:51       ` Daniel Gryniewicz
2007-05-02  6:49         ` Danny van Dyk
2007-05-02 11:56         ` Ciaran McCreesh
2007-05-01 23:56   ` Ciaran McCreesh
2007-05-02 10:54   ` Philipp Riegger
2007-05-02 20:05 ` Mike Frysinger
2007-05-02 20:12   ` Ciaran McCreesh
2007-05-06  8:39     ` Mike Frysinger
2007-05-05 21:17 ` [gentoo-dev] tests Ryan Hill
2007-05-06  4:27   ` Alistair John Bush

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=200705011508.57220.peper@gentoo.org \
    --to=peper@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