From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage-utils:master commit in: tests/
Date: Mon, 25 May 2020 18:40:13 +0000 (UTC) [thread overview]
Message-ID: <1590431929.93ab3a3b0a280d83d5d65af2e4740cb3227a38a2.grobian@gentoo> (raw)
commit: 93ab3a3b0a280d83d5d65af2e4740cb3227a38a2
Author: Fabian Groffen <grobian <AT> gentoo <DOT> org>
AuthorDate: Mon May 25 18:38:49 2020 +0000
Commit: Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Mon May 25 18:38:49 2020 +0000
URL: https://gitweb.gentoo.org/proj/portage-utils.git/commit/?id=93ab3a3b
tests/init: drop valgrind exclusions
After some manual testing and fixes on a Bionic VM, valgrind no longer
dumps core there, so let's hope we can finally run the full suite using
valgrind on Travis too.
Signed-off-by: Fabian Groffen <grobian <AT> gentoo.org>
tests/init.sh.in | 2 --
1 file changed, 2 deletions(-)
diff --git a/tests/init.sh.in b/tests/init.sh.in
index 8b67070..6cdfccf 100644
--- a/tests/init.sh.in
+++ b/tests/init.sh.in
@@ -35,8 +35,6 @@ q -i -q
# used by Travis segfaults on qmanifest and qcheck, so disable there to
# be able to run the rest regularly
dovalgrind=${Q_RUN_WITH_VALGRIND}
-[[ ${TRAVIS_OS_NAME}:${as##*/} == linux:qmanifest ]] && dovalgrind=
-[[ ${TRAVIS_OS_NAME}:${as##*/} == linux:qcheck ]] && dovalgrind=
if [[ -n ${dovalgrind} ]] ; then
chmod 755 "@abs_top_srcdir@/tests/valgrind-wrapper/qvalgrind"
for f in @abs_top_builddir@/q?* ; do
next reply other threads:[~2020-05-25 18:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 18:40 Fabian Groffen [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-02-06 15:32 [gentoo-commits] proj/portage-utils:master commit in: tests/ Fabian Groffen
2021-12-27 18:13 Fabian Groffen
2021-12-23 12:55 Fabian Groffen
2021-12-13 8:39 Fabian Groffen
2020-05-25 19:15 Fabian Groffen
2020-05-25 19:06 Fabian Groffen
2020-01-18 13:09 Fabian Groffen
2020-01-02 21:25 Fabian Groffen
2020-01-02 20:48 Fabian Groffen
2019-06-10 10:09 Fabian Groffen
2015-06-03 15:44 Mike Frysinger
2015-02-21 18:06 Mike Frysinger
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=1590431929.93ab3a3b0a280d83d5d65af2e4740cb3227a38a2.grobian@gentoo \
--to=grobian@gentoo.org \
--cc=gentoo-commits@lists.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