On Tue, May 17, 2016 at 12:05 PM, Sébastien Fabbro <bicat...@gentoo.org> wrote: > On 17 May 2016 at 08:34, Luis Ressel <ara...@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
