From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] FEATURES=test, sys-devel/gcc ignored test failures
Date: Mon, 21 Mar 2011 13:07:33 +0100 [thread overview]
Message-ID: <4D873F85.5070203@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 564 bytes --]
sys-devel/gcc runs tests, but the results are ignored and I remember the
tests fail most of the time.
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:
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?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
next reply other threads:[~2011-03-21 12:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 12:07 "Paweł Hajdan, Jr." [this message]
2011-03-21 12:29 ` [gentoo-dev] FEATURES=test, sys-devel/gcc ignored test failures Amadeusz Żołnowski
2011-03-21 22:02 ` [gentoo-dev] " Ryan Hill
2011-03-22 12:09 ` "Paweł Hajdan, Jr."
2011-03-22 15:01 ` Matt Turner
2011-03-22 23:25 ` Ryan Hill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D873F85.5070203@gentoo.org \
--to=phajdan.jr@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox