| 1 |
On Tue, May 17, 2016 at 12:05 PM, Sébastien Fabbro <bicatali@g.o> wrote: |
| 2 |
> On 17 May 2016 at 08:34, Luis Ressel <aranea@×××××.de> wrote: |
| 3 |
> |
| 4 |
>> |
| 5 |
>> Automated post-merge tests sound kinda dangerous to me. And I don't |
| 6 |
>> think there's any stipulation about src_test() only running |
| 7 |
>> upstream-provided test suites. IMHO, src_test() would be a good place |
| 8 |
>> for most of the maintainter-provided tests you have in mind. |
| 9 |
>> |
| 10 |
> |
| 11 |
> The idea of this project is not for a typical Gentoo user to run this |
| 12 |
> post-merge test, but for an automated arch-tester bot to run them in |
| 13 |
> batch jobs. The result of which would be an update of the ebuild to |
| 14 |
> stable. |
| 15 |
|
| 16 |
I would suggest that it would make sense to separate tests that are |
| 17 |
unsafe for a typical user to run from those which are, to allow users |
| 18 |
to run them if they so choose. As I said earlier, arch testing has |
| 19 |
its limitations and I think many would like to be able to run the |
| 20 |
automated tests routinely. Since they're standardized they'd also |
| 21 |
provide really good feedback to maintainers when they do have errors |
| 22 |
missed by ATs. |
| 23 |
|
| 24 |
-- |
| 25 |
Rich |
Archives