On Mon, 21 Mar 2011 13:07:33 +0100 "Paweł Hajdan, Jr." <phajdan...@gentoo.org> wrote:
> sys-devel/gcc runs tests, but the results are ignored and I remember the
> tests fail most of the time.
s/most/all
> Because the tests take long time to run and fail anyway (I understand
> it's non-trivial to fix those on Gentoo side), I wonder whether it makes
> sense to run them at all:
It does to me, I use them all the time. ;) The important part is that we
install the test results, which can then be used for regression testing when
rolling patchsets.
> toolchain.eclass:
>
> gcc_src_test() {
> cd "${WORKDIR}"/build
> emake -j1 -k check || ewarn "check failed and that sucks :("
> }
>
> My suggestion is to make the src_test empty (I think the default one
> still calls make). I can produce a patch if needed.
>
> What do you think?
I think that glibc and gcc tests and other testsuites that nearly always
fail shouldn't be run for the average user but should still be easily
accessible in a standard way. I think we need a more finely grained test
setup, where we can say tests are "expensive" or "interesting only to
developers" or "known to fail", and let people opt-in to these on a
per-package basis. Right now you always have to opt-out using
package.use.mask which "works" but is unintuitive.
--
fonts, gcc-porting, it makes no sense how it makes no sense
toolchain, wxwidgets but i'll take it free anytime
@ gentoo.org EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
signature.asc
Description: PGP signature
