public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] EAPI 3 PMS Draft
Date: Tue, 17 Mar 2009 10:50:17 +0300	[thread overview]
Message-ID: <1237276217.31676.3403.camel@localhost> (raw)
In-Reply-To: <20090316204717.699511f0@snowcone>

[-- Attachment #1: Type: text/plain, Size: 703 bytes --]

В Пнд, 16/03/2009 в 20:47 +0000, Ciaran McCreesh пишет:
> * Am I to take it src_test is to remain in its current worthless state?

Is it possible in EAPI 3 make src_test failures not fatal? Something
like make die() non fatal inside src_test. Package manager if it sees
die() inside src_test should remember this failure and warn people at
the end of merge that tests failed. It's wise to preserve output of
failed tests somewhere and may be introduce with some
FEATURES=tests-keepwork.

Probably this is not best implementation, but it describes idea well. If
failures are non fatal I don't object to having src_test enabled by
default and I'll all for this even.

-- 
Peter.

[-- Attachment #2: Эта часть сообщения подписана цифровой подписью --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2009-03-17  7:52 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 20:47 [gentoo-dev] EAPI 3 PMS Draft Ciaran McCreesh
2009-03-16 22:59 ` Maciej Mrozowski
2009-03-16 23:09   ` Rémi Cardona
2009-03-16 23:20   ` Ciaran McCreesh
2009-03-16 23:26     ` Tomáš Chvátal
2009-03-16 23:35       ` Ciaran McCreesh
2009-03-17  0:05         ` Jorge Manuel B. S. Vicetto
2009-03-17  0:17           ` Ciaran McCreesh
2009-03-17  0:46   ` Thomas Anderson
2009-03-17  4:07     ` Nirbheek Chauhan
2009-03-16 23:22 ` Tiziano Müller
2009-03-16 23:51   ` [gentoo-dev] " Ryan Hill
2009-03-16 23:54     ` Ciaran McCreesh
2009-03-17  2:47       ` Ryan Hill
2009-04-23  5:32         ` Donnie Berkholz
2009-04-23  6:05           ` Nirbheek Chauhan
2009-03-17  4:45     ` Luca Barbato
2009-03-17  6:47   ` [gentoo-dev] " Ulrich Mueller
2009-03-17  8:15     ` Tiziano Müller
2009-03-17  8:57       ` Ulrich Mueller
2009-03-17 13:55         ` Ciaran McCreesh
2009-03-17 15:11           ` Ulrich Mueller
2009-03-17 15:23             ` Ciaran McCreesh
2009-03-17  8:21   ` Tiziano Müller
2009-03-17  7:50 ` Peter Volkov [this message]
2009-03-17  8:05   ` Ulrich Mueller
2009-03-17  8:19     ` Tiziano Müller
2009-03-17 13:54     ` Ciaran McCreesh
2009-03-17 13:55   ` Ciaran McCreesh
2009-04-09  1:12     ` Mart Raudsepp
2009-04-09 14:37       ` Ciaran McCreesh
2009-04-09 16:20         ` Mart Raudsepp
2009-04-09 16:25           ` Ciaran McCreesh
2009-04-11 18:56             ` Alistair Bush
2009-04-11 19:10           ` [gentoo-dev] " Ryan Hill
2009-04-09 16:21         ` [gentoo-dev] " Patrick Lauer
2009-04-09 16:29           ` Ciaran McCreesh
2009-04-09 17:13             ` Richard Freeman
2009-04-09 19:24               ` Tiziano Müller
2009-04-10 10:03         ` [gentoo-dev] " Christian Faulhammer
2009-04-11  3:54           ` James Rowe
2009-04-11 10:57             ` Marijn Schouten (hkBst)
2009-04-11 12:09               ` James Rowe
2009-04-11 19:08       ` [gentoo-dev] " Alistair Bush
2009-03-17 15:47 ` [gentoo-dev] " Ciaran McCreesh
2009-03-27  9:40 ` [gentoo-dev] " Fabian Groffen

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=1237276217.31676.3403.camel@localhost \
    --to=pva@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