From: "Mike Frysinger" <vapier@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gcc-config:master commit in: tests/
Date: Sun, 30 Dec 2012 23:24:02 +0000 (UTC) [thread overview]
Message-ID: <1356909907.fbfb0cc589e7ef8e3d61d4ccf8038356c2b5f2bc.vapier@gentoo> (raw)
commit: fbfb0cc589e7ef8e3d61d4ccf8038356c2b5f2bc
Author: Fabian Groffen <grobian <AT> gentoo <DOT> org>
AuthorDate: Sun Dec 30 15:46:09 2012 +0000
Commit: Mike Frysinger <vapier <AT> gentoo <DOT> org>
CommitDate: Sun Dec 30 23:25:07 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/gcc-config.git;a=commit;h=fbfb0cc5
run_test: set RC_NOCOLOR to suppress colours
NOCOLOR appears not to work with functions.sh from baselayout-prefix,
which is an old copy, prior to 2.0. Not sure if this patch is really
worth it, since the output of functions.sh also differs enough to make
tests fail.
Signed-off-by: Fabian Groffen <grobian <AT> gentoo.org>
Signed-off-by: Mike Frysinger <vapier <AT> gentoo.org>
---
tests/run_tests | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/tests/run_tests b/tests/run_tests
index 1d35d9f..caca986 100755
--- a/tests/run_tests
+++ b/tests/run_tests
@@ -18,7 +18,7 @@ if ! . /etc/init.d/functions.sh 2>/dev/null ; then
die() { echo "$*"; exit 1; }
fi
-vars=( CHOST GCC_CONFIG ROOT TROOT NOCOLOR )
+vars=( CHOST GCC_CONFIG ROOT TROOT NOCOLOR RC_NOCOLOR )
unset ${vars[@]}
TROOT=${PWD}
@@ -29,6 +29,7 @@ fi
PATH="${TROOT}/..:${PATH}"
NOCOLOR="true"
+RC_NOCOLOR="yes" # Older baselayout/openrc versions.
# This CHOST value doesn't matter. It could be anything.
# As long as all the configs we test are based on this being
# the CHOST value.
next reply other threads:[~2012-12-30 23:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-30 23:24 Mike Frysinger [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-31 0:34 [gentoo-commits] proj/gcc-config:master commit in: tests/ Mike Frysinger
2012-12-31 1:18 Mike Frysinger
2015-05-13 4:26 Ryan Hill
2018-08-13 21:58 Sergei Trofimovich
2022-09-22 23:46 Sam James
2024-12-08 3:18 Sam James
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=1356909907.fbfb0cc589e7ef8e3d61d4ccf8038356c2b5f2bc.vapier@gentoo \
--to=vapier@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