1 |
> Is there any kind of QA tool that normal end users can contribute CPU |
2 |
> cycles to? Given the massive combinatorial explosion of package |
3 |
> configurations that can be installed using Gentoo, one might imagine |
4 |
> that there's some value in simply installing programs with different |
5 |
> USE combinations and running the self-tests for those programs. |
6 |
|
7 |
The Perl community has had CPAN::Reporter for a while and a set of |
8 |
smoke-test machines that run it. Normal Perl installs run "make test" |
9 |
as part of the normal install, the reporter feeds back test results |
10 |
to the authors -- I get a daily report of what failed and where. The |
11 |
smoke-test servers run CPAN::Reporter on whatever gets checked in each |
12 |
day. |
13 |
|
14 |
In today's world it's rather easy to set this up with docker, using |
15 |
Gentoo and some temp volumes (e.g., example using Gentoo for smoke- |
16 |
testing CPAN: https://www.slideshare.net/lembark/smoking-docker). |
17 |
|
18 |
Adding a Reporter-ish layer to a new version of Portage or a smoke- |
19 |
testing option that does a "emerge --install" into a temp layer in |
20 |
Docker, reports the outcome, and discards the results shouldn't be |
21 |
all that hard. |
22 |
|
23 |
I'd be happy to work on something like this. |
24 |
|
25 |
-- |
26 |
Steven Lembark 5725 Aylesboro Ave |
27 |
Workhorse Computing Pittsburgh PA 15217 |
28 |
lembark@×××××××.com +1 888 359 3508 |