public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: rschiele@uni-mannheim.de
To: gcc-gnats@gcc.gnu.org
Subject: other/10819: testsuite creates CR+LF on compiler version lines in test summary files
Date: Fri, 16 May 2003 15:26:00 -0000	[thread overview]
Message-ID: <20030516151813.6821.qmail@sources.redhat.com> (raw)


>Number:         10819
>Category:       other
>Synopsis:       testsuite creates CR+LF on compiler version lines in test summary files
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri May 16 15:26:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Robert Schiele
>Release:        3.3, 3.3.1 20030515 (prerelease), 3.4 20030515 (experimental)
>Organization:
>Environment:
Seems to be independent of environment. I have it on all my platforms. Might depend on dejagnu/expect releases. If you can't reproduce, ask for additional information you need.
>Description:
The testsuite creates CR+LF on compiler version lines in test summary files like:

/local/build/gcc/testsuite/../g++ version 3.3 <== HERE

This confuses some implementations of Mail and thus they send the report as a binary attachment. Results can be seen here: http://gcc.gnu.org/ml/gcc-testresults/2003-05/msg00946.html
>How-To-Repeat:
Run the testsuite and inspect one of the summary files.
>Fix:
Workaround: Place some sed/awk/whatever command into contrib/test_results to filter this rubbish out, but the better way would be to prevent the testsuite from behaving this way, but I do not know dejagnu enough to identify the real problem here.
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2003-05-16 15:26 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=20030516151813.6821.qmail@sources.redhat.com \
    --to=rschiele@uni-mannheim.de \
    --cc=gcc-gnats@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).