From: "Ryan Hill" <rhill@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gcc-config:master commit in: tests/
Date: Wed, 13 May 2015 04:26:56 +0000 (UTC) [thread overview]
Message-ID: <1431490168.d45de09450ffb63b138bbb7f78cae43e1101e2ec.rhill@gentoo> (raw)
commit: d45de09450ffb63b138bbb7f78cae43e1101e2ec
Author: Ryan Hill <rhill <AT> gentoo <DOT> org>
AuthorDate: Wed May 13 04:09:28 2015 +0000
Commit: Ryan Hill <rhill <AT> gentoo <DOT> org>
CommitDate: Wed May 13 04:09:28 2015 +0000
URL: https://gitweb.gentoo.org/proj/gcc-config.git/commit/?id=d45de094
Ignore whitespace when diffing test results.
The amount of whitespace output by ebegin/eend from gentoo-functions
is dynamic (seems to be dependent on terminal width). Since we can't
predict this we have to ignore all whitespace differences.
URL: https://bugs.gentoo.org/547586
Reported-by: tka <tka <AT> kamph.org>
Signed-off-by: Ryan Hill <rhill <AT> gentoo.org>
tests/run_tests | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/run_tests b/tests/run_tests
index 2ff7d77..397d667 100755
--- a/tests/run_tests
+++ b/tests/run_tests
@@ -44,7 +44,7 @@ cmp_log() {
args+=( -e "s|: line [0-9]*: |: |g" )
sed "${args[@]}" "${exp}" > "${exp}.tmp"
sed "${args[@]}" "${log}" > "${log}.tmp"
- diff -u "${exp}.tmp" "${log}.tmp" > "${log}.diff"
+ diff -uw "${exp}.tmp" "${log}.tmp" > "${log}.diff"
ret=$?
rm "${exp}.tmp"
return ${ret}
next reply other threads:[~2015-05-13 4:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 4:26 Ryan Hill [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-08 3:18 [gentoo-commits] proj/gcc-config:master commit in: tests/ Sam James
2022-09-22 23:46 Sam James
2018-08-13 21:58 Sergei Trofimovich
2012-12-31 1:18 Mike Frysinger
2012-12-31 0:34 Mike Frysinger
2012-12-30 23:24 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=1431490168.d45de09450ffb63b138bbb7f78cae43e1101e2ec.rhill@gentoo \
--to=rhill@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