| 1 |
On Sat, Aug 05, 2006 at 02:26:16AM +0200, Jakub Moc wrote: |
| 2 |
> Kevin F. Quinn wrote: |
| 3 |
> > I'd like to suggest we make FEATURES=test (and therefore USE=test) the |
| 4 |
> > default behaviour, rather than the opt-in we currently have. Far too |
| 5 |
> > many packages fail their test phase. |
| 6 |
> |
| 7 |
> Sure everyone likes to watch glibc failing? :P </joke> |
| 8 |
> |
| 9 |
> Well, can't be done until bugs such as |
| 10 |
> http://bugs.gentoo.org/show_bug.cgi?id=69343 are solved (at least as in |
| 11 |
> sticking RESTRICT=test there) instead of being ignored. |
| 12 |
> |
| 13 |
> > At the very least, ebuild maintainers and ATs should be running with |
| 14 |
> > tests switched on. If the tests are known to fail then the ebuild can |
| 15 |
> > either RESTRICT=test, or just return successfully from src_test() |
| 16 |
> > where the test report is useful even if some tests fail. |
| 17 |
> |
| 18 |
> See above. And even then, I don't think it's a good idea to force this |
| 19 |
> upon users. Lots of packages have tests that are very time-consuming, |
| 20 |
> and there are packages that always fail tests and it's pretty much |
| 21 |
> expected (PHP is one of them; and while the failure isn't fatal there, |
| 22 |
> it still takes tons of time to go thru those ~2000 tests). And there are |
| 23 |
> tons of packages where tests are more or less unmaintained. |
| 24 |
|
| 25 |
Agreed. It may be better to instead have a FORCE="test" on certain |
| 26 |
ebuilds (mainly sci-* stuff where you want to be sure the numbers are |
| 27 |
coming out correctly) -- adding FEATURES="test" to the default set |
| 28 |
will cause serious breakage and will take quite some time to be |
| 29 |
fully fixed across the whole tree. |
| 30 |
-- |
| 31 |
gentoo-dev@g.o mailing list |
Archives