| 1 |
On Sat, 5 Aug 2006 02:39:16 +0200 |
| 2 |
Danny van Dyk <kugelfang@g.o> wrote: |
| 3 |
|
| 4 |
> Am Samstag, 5. August 2006 02:11 schrieb Kevin F. Quinn: |
| 5 |
> > At the very least, ebuild maintainers and ATs should be running with |
| 6 |
> > tests switched on. If the tests are known to fail then the ebuild |
| 7 |
> > can either RESTRICT=test, or just return successfully from |
| 8 |
> > src_test() where the test report is useful even if some tests fail. |
| 9 |
> > |
| 10 |
> > Thoughts? |
| 11 |
> * autoconf takes ages (longer than compiling glibc here). |
| 12 |
> * glibc tests fail on amd64 since at least a year. |
| 13 |
> * automake|e2fsprogs|neon|gettext|tar have failed tests for me more |
| 14 |
> than once. |
| 15 |
> |
| 16 |
> As soon as these are fixed, i wouldn't mind making FEATURES="test" a |
| 17 |
> default. |
| 18 |
|
| 19 |
Well, if something fails its tests but you still want it regardless or |
| 20 |
you want to skip the test phase for some other reason, you can always |
| 21 |
do FEATURES="-test" emerge <foo>. |
| 22 |
|
| 23 |
Changing the default doesn't prevent people from skipping tests, |
| 24 |
however in the long term it will reduce the amount of stuff committed |
| 25 |
to the tree that doesn't pass tests. It will increase the amount of |
| 26 |
times a system or world update falls over, but changing the default |
| 27 |
will raise the priority for getting these things fixed. |
| 28 |
|
| 29 |
There are many packages in the tree for which it is clear the |
| 30 |
maintainer did not even attempt to run the tests - e.g. |
| 31 |
https://bugs.gentoo.org/show_bug.cgi?id=139414 To my mind committing |
| 32 |
packages without even bothering to try the test phase is inexcusable. |
| 33 |
|
| 34 |
-- |
| 35 |
Kevin F. Quinn |
Archives