public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Emrich <rainer@emrich-ebersheim.de>
To: gcc Mailing List <gcc@gcc.gnu.org>
Subject: Status of 9.0.1 20190415 [trunk revision 270358] on x86_64-w64-mingw32
Date: Mon, 15 Apr 2019 15:22:00 -0000	[thread overview]
Message-ID: <d9a1dd73-2fdf-c705-c495-87eb7c31d8c9@emrich-ebersheim.de> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2033 bytes --]

Today I had the chance to bootstrap and runthe testsuite for trunk on
x86_64-w64-mingw32. Bootstrap is done with all supported languages
enabled including "D".

Testsuite results can be found here:
https://gcc.gnu.org/ml/gcc-testresults/2019-04/msg01795.html

Complete logs here:
https://cloud.emrich-ebersheim.de/index.php/s/g9D245XdCW6GD5W

There's are two issues with the gdc testsuite.
1. The failed tests are printed twenty times to the test_summary.txt file.

2. couldn't open "gdc.test/compilable/99bottles.d"
ERROR: tcl error sourcing
/opt/devel/gnu/src/gcc-mingw-w64/gcc-9.0.1/gcc/testsuite/gdc.test/gdc-test.exp.
ERROR: couldn't open "gdc.test/compilable/99bottles.d": no such file or
directory
    while executing
"open $file r"
    (procedure "grep" line 19)
    invoked from within
"grep $prog "{\[ \t\]\+dg-\[-a-z\]\+\[ \t\]\+.*\[ \t\]\+}" line"
    (procedure "dg-get-options" line 4)
    invoked from within
"dg-get-options $prog"
    (procedure "saved-dg-test" line 75)
    invoked from within
"saved-dg-test gdc.test/compilable/99bottles.d { }
-I/opt/devel/gnu/src/gcc-mingw-w64/gcc-9.0.1/gcc/testsuite/gdc.test/compilable"
    ("eval" body line 1)
    invoked from within
"eval saved-dg-test $args "
    (procedure "dg-test" line 4)
    invoked from within
"dg-test $test "$flags $flags_t" ${default-extra-flags}"
    (procedure "gdc-dg-runtest" line 23)
    invoked from within
"gdc-dg-runtest $filename $flags $imports"
    (procedure "gdc-do-test" line 86)
    invoked from within
"gdc-do-test"
    (file
"/opt/devel/gnu/src/gcc-mingw-w64/gcc-9.0.1/gcc/testsuite/gdc.test/gdc-test.exp"
line 465)
    invoked from within
"source
/opt/devel/gnu/src/gcc-mingw-w64/gcc-9.0.1/gcc/testsuite/gdc.test/gdc-test.exp"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 source
/opt/devel/gnu/src/gcc-mingw-w64/gcc-9.0.1/gcc/testsuite/gdc.test/gdc-test.exp"
    invoked from within
"catch "uplevel #0 source $test_file_name""

Hope this is of any help


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2019-04-15 15:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 15:22 Rainer Emrich [this message]
2019-04-15 15:30 ` Rainer Emrich
2019-04-15 15:38   ` Jakub Jelinek
2019-04-15 15:43     ` Rainer Emrich
2019-04-15 18:12       ` Rainer Emrich
2019-04-16  9:59         ` Rainer Emrich
2019-04-16 11:04           ` dg-extract-results broken since rev 268511, was " Rainer Emrich
2019-04-16 12:11             ` Christophe Lyon
2019-04-16 12:35               ` Rainer Emrich
2019-04-16 12:49                 ` Christophe Lyon
2019-04-16 13:00                   ` Rainer Emrich
2019-04-16 13:44                   ` Jakub Jelinek
2019-04-16 15:36                     ` Jakub Jelinek
2019-04-16 15:57                       ` Rainer Emrich
2019-04-16 19:27                       ` Christophe Lyon
2019-04-16 15:48                     ` Martin Jambor

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=d9a1dd73-2fdf-c705-c495-87eb7c31d8c9@emrich-ebersheim.de \
    --to=rainer@emrich-ebersheim.de \
    --cc=gcc@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).