| 1 |
On Friday 13 April 2007, Ciaran McCreesh wrote: |
| 2 |
> Joshua Jackson <tsunam@g.o> wrote: |
| 3 |
> > Erm, no I have not at all (speaking as a project lead for x86). Test |
| 4 |
> > is not viable for a lot of reason as being on by default. One that I |
| 5 |
> > can come up with off the top of my head is php. The test suite for it |
| 6 |
> > makes test inadvisable on any desktop system, I'd say the same for a |
| 7 |
> > server as well. Not to mention that a lot of upstream test functions |
| 8 |
> > are in fact themselves broken because they require dependencies that |
| 9 |
> > are not required for the application itself. This is not a simple |
| 10 |
> > case of downstream (being gentoo) doing this. There has to be quite a |
| 11 |
> > bit changed for test to be viable and even then I don't think it |
| 12 |
> > really is unfortunately due to test packages that can take 12+ hours |
| 13 |
> > on a decently equipped modern system. |
| 14 |
> |
| 15 |
> If a test suite isn't viable, the ebuild should be RESTRICTing test |
| 16 |
> anyway. |
| 17 |
|
| 18 |
which doesnt apply here ... some packages have ridiculous awesome coverage for |
| 19 |
their source code and take much longer to run than even compile the package |
| 20 |
|
| 21 |
care to force mysql test suites on everyone ? php ? gcc ? binutils ? |
| 22 |
-mike |
Archives