From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] Proposal for changes for the next EAPI version
Date: Tue, 17 May 2016 12:42:15 -0400 [thread overview]
Message-ID: <CAGfcS_=X4x=YXj8yiKLq8TJUBsWckEKqwuLX4p_oZeK+fqd60Q@mail.gmail.com> (raw)
In-Reply-To: <CAA-OU2p2KuMdE8A99=rcaF_31hqTieTpD9Z5D6AY2rsYvq41fw@mail.gmail.com>
On Tue, May 17, 2016 at 12:05 PM, Sébastien Fabbro <bicatali@gentoo.org> wrote:
> On 17 May 2016 at 08:34, Luis Ressel <aranea@aixah.de> wrote:
>
>>
>> Automated post-merge tests sound kinda dangerous to me. And I don't
>> think there's any stipulation about src_test() only running
>> upstream-provided test suites. IMHO, src_test() would be a good place
>> for most of the maintainter-provided tests you have in mind.
>>
>
> The idea of this project is not for a typical Gentoo user to run this
> post-merge test, but for an automated arch-tester bot to run them in
> batch jobs. The result of which would be an update of the ebuild to
> stable.
I would suggest that it would make sense to separate tests that are
unsafe for a typical user to run from those which are, to allow users
to run them if they so choose. As I said earlier, arch testing has
its limitations and I think many would like to be able to run the
automated tests routinely. Since they're standardized they'd also
provide really good feedback to maintainers when they do have errors
missed by ATs.
--
Rich
next prev parent reply other threads:[~2016-05-17 16:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 12:43 [gentoo-dev] Proposal for changes for the next EAPI version Pallav Agarwal
2016-05-16 16:38 ` Luis Ressel
2016-05-17 7:37 ` Pallav Agarwal
2016-05-17 8:02 ` Kent Fredric
2016-05-17 8:46 ` Tobias Klausmann
2016-05-17 9:15 ` Kent Fredric
2016-05-17 10:57 ` Rich Freeman
2016-05-17 11:25 ` Pallav Agarwal
2016-05-17 11:42 ` Rich Freeman
2016-05-17 10:01 ` Pallav Agarwal
2016-05-17 11:26 ` Michael Orlitzky
2016-05-17 11:29 ` Ciaran McCreesh
2016-05-18 8:18 ` [gentoo-dev] " Duncan
2016-05-17 13:53 ` [gentoo-dev] " M.B.
2016-05-17 14:02 ` Brian Dolbec
2016-05-17 15:34 ` Luis Ressel
2016-05-17 16:05 ` Sébastien Fabbro
2016-05-17 16:42 ` Rich Freeman [this message]
2016-05-18 0:14 ` Kent Fredric
2016-05-18 0:35 ` M. J. Everitt
2016-05-18 0:44 ` Kent Fredric
2016-05-18 0:48 ` M. J. Everitt
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='CAGfcS_=X4x=YXj8yiKLq8TJUBsWckEKqwuLX4p_oZeK+fqd60Q@mail.gmail.com' \
--to=rich0@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