1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Kevin F. Quinn wrote: |
5 |
> I'd like to suggest we make FEATURES=test (and therefore USE=test) the |
6 |
> default behaviour, rather than the opt-in we currently have. Far too |
7 |
> many packages fail their test phase. |
8 |
> |
9 |
> Since we encourage users to set CFLAGS in ways that upstream may not |
10 |
> have predicted, if upstream go to the trouble of providing tests it |
11 |
> seems sensible to me that they should be run, unless there is a very |
12 |
> good reason not to run them. This will help pick up faults that are due |
13 |
> to the compiler version, CFLAGS etc much more consistently. |
14 |
> |
15 |
> At the very least, ebuild maintainers and ATs should be running with |
16 |
> tests switched on. If the tests are known to fail then the ebuild can |
17 |
> either RESTRICT=test, or just return successfully from src_test() |
18 |
> where the test report is useful even if some tests fail. |
19 |
> |
20 |
> Thoughts? |
21 |
I can say from experience that there are a great heaping load of |
22 |
packages currently that fail their test suite, the sci-team seems to |
23 |
be the best in this regard for passing the tests successfully. If we |
24 |
do in fact plan on making this the default, we should be prepared for |
25 |
a increase in bugs from users who will now have ebuilds stop on |
26 |
failed test suites. While I agree that it would be nice to see more |
27 |
people using test and collision-protect I don't think its something we |
28 |
should enable at this point in time till we have many packages working |
29 |
correctly with the feature. If however people feel that by enabling |
30 |
it, that it'll make us actually fix these issues then I'd like to see |
31 |
it move forward. I'm just curious as to why this has come up suddenly |
32 |
Kevin? |
33 |
|
34 |
p.s I hope all dev's run with test and collision-protect, I know I |
35 |
know you don't but I can hope. |
36 |
-----BEGIN PGP SIGNATURE----- |
37 |
Version: GnuPG v1.4.5 (GNU/Linux) |
38 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
39 |
|
40 |
iD8DBQFE0+VtSENan+PfizARAhNtAKCclIg8ikGcaTgQ9E5YPBjPj93IlACeJyNX |
41 |
ER9yFoXQ3hOKzoMq4OxL3Rg= |
42 |
=uS4D |
43 |
-----END PGP SIGNATURE----- |
44 |
|
45 |
-- |
46 |
gentoo-dev@g.o mailing list |