public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Danny van Dyk <kugelfang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] tests
Date: Wed, 2 May 2007 08:53:32 +0200	[thread overview]
Message-ID: <200705020853.32461.kugelfang@gentoo.org> (raw)
In-Reply-To: <46382875.7030407@gentoo.org>

Am Mittwoch, 2. Mai 2007 schrieb Rémi Cardona:
> Piotr Jaroszyński a écrit :
> > On Tuesday 01 of May 2007 21:53:36 Maurice van der Pot wrote:
> >> I'm not sure why this is a reply to my message instead of the
> >> message I replied to. They both provide more or less the same
> >> choice to the user.
> >
> > Err I wasn't providing any choices for users yet, I only thought
> > about the below as things that can be wanted by users/devs and
> > asked whether I missed something. How we will end up distinguishing
> > them is another story...
> >
> >> - run all tests
> >> - run only reasonable tests
> >> - run only necessary tests
> >> - don't run tests at all
>
> Philosophical question :
>
> What's "reasonable"? Where do you draw the line? Same question for
> "necessary".
Re 'necessary': Tests for scientific packages are surely necessary, i'd 
even claim they're mandatory. Nothing is as bad as having a program 
that yields unreproducable (read: wrong) results.

Been there, seen that, had the primordial urge to kill things.

Danny
-- 
Danny van Dyk <kugelfang@gentoo.org>
Gentoo/AMD64 Project, Gentoo Scientific Project
--
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2007-05-02  6:56 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 13:08 [gentoo-dev] tests Piotr Jaroszyński
2007-05-01 13:24 ` 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 [this message]
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=200705020853.32461.kugelfang@gentoo.org \
    --to=kugelfang@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