public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Iain D Sandoe <iains@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r11-11392] testsuite, asan: Avoid color in asan test output.
Date: Sun, 28 Apr 2024 14:42:04 +0000 (GMT)	[thread overview]
Message-ID: <20240428144204.3A4A43858D20@sourceware.org> (raw)

https://gcc.gnu.org/g:57596bb82e31d2dfdba2eb41c16e45a9bbeb38a7

commit r11-11392-g57596bb82e31d2dfdba2eb41c16e45a9bbeb38a7
Author: Iain Sandoe <iain@sandoe.co.uk>
Date:   Sun Jun 19 10:31:01 2022 +0100

    testsuite, asan: Avoid color in asan test output.
    
    The presence of the color markers in the some of the asan tests
    appears to confuse the dg-output matching (possibly a platform
    TCL or termios bug) on some Darwin platforms.
    
    Since the color is not being tested, switch it off (makes the log
    files easier to read too).  This fixes a large number of spurious
    test fails on AVX512 Darwin19.
    
    Signed-off-by: Iain Sandoe <iain@sandoe.co.uk>
    
    gcc/testsuite/ChangeLog:
    
            * lib/asan-dg.exp: Do not apply color to asan output when
            under test.
    
    (cherry picked from commit 607118dfa47a1865dc59f98e7d161da98471d688)

Diff:
---
 gcc/testsuite/lib/asan-dg.exp | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/gcc/testsuite/lib/asan-dg.exp b/gcc/testsuite/lib/asan-dg.exp
index e926dc3ad03..954b0ae22d4 100644
--- a/gcc/testsuite/lib/asan-dg.exp
+++ b/gcc/testsuite/lib/asan-dg.exp
@@ -111,6 +111,8 @@ proc asan_init { args } {
     global asan_saved_TEST_ALWAYS_FLAGS
     global asan_saved_ALWAYS_CXXFLAGS
 
+    setenv ASAN_OPTIONS "color=never"
+
     set link_flags ""
     if ![is_remote host] {
 	if [info exists TOOL_OPTIONS] {

                 reply	other threads:[~2024-04-28 14:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20240428144204.3A4A43858D20@sourceware.org \
    --to=iains@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).