From: Rainer Emrich <rainer@emrich-ebersheim.de>
To: Jakub Jelinek <jakub@redhat.com>
Cc: gcc Mailing List <gcc@gcc.gnu.org>
Subject: Re: Status of 9.0.1 20190415 [trunk revision 270358] on x86_64-w64-mingw32
Date: Mon, 15 Apr 2019 15:43:00 -0000 [thread overview]
Message-ID: <34226dcf-24e4-370f-0f88-a69d979aef2e@emrich-ebersheim.de> (raw)
In-Reply-To: <20190415153842.GU21066@tucnak>
[-- Attachment #1.1: Type: text/plain, Size: 694 bytes --]
Am 15.04.2019 um 17:38 schrieb Jakub Jelinek:
> On Mon, Apr 15, 2019 at 05:30:14PM +0200, Rainer Emrich wrote:
>> There seems to be a generic issue with the tests in gcc/testsuite. The
>> log files do not contain the logs.
>
> Perhaps contrib/dg-extract-results* misbehaved?
> Can you look for the testsuite/g++*/g++.log.sep files? Do they contain
> everything?
> If yes, can you try to say
> mv contrib/dg-extract-results.py{,.bad}
> and retry, to see if there isn't a problem with the python version thereof?
Unfortunately I already deleted the build directory.
So, I will run a new bootstrap an testsuite run reduced with reduced
languages. Will take some hours.
Rainer
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-04-15 15:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 15:22 Rainer Emrich
2019-04-15 15:30 ` Rainer Emrich
2019-04-15 15:38 ` Jakub Jelinek
2019-04-15 15:43 ` Rainer Emrich [this message]
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=34226dcf-24e4-370f-0f88-a69d979aef2e@emrich-ebersheim.de \
--to=rainer@emrich-ebersheim.de \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
/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).