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. Basically CI for ebuilds: it could be implemented as a script living in the package directory, something like a .travis.yml in the GitHub repositories or may be an EAPI change. Debian has a similar project [1]. Upstream could provide CI tests and sometimes they do, but we want to make sure the package integrates well in an installed Gentoo distribution. [1] https://ci.debian.net/doc/ Sebastien
