public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christophe Lyon <christophe.lyon@linaro.org>
To: Rainer Emrich <rainer@emrich-ebersheim.de>
Cc: Jakub Jelinek <jakub@redhat.com>, gcc Mailing List <gcc@gcc.gnu.org>
Subject: Re: dg-extract-results broken since rev 268511, was Re: Status of 9.0.1 20190415 [trunk revision 270358] on x86_64-w64-mingw32
Date: Tue, 16 Apr 2019 12:49:00 -0000	[thread overview]
Message-ID: <CAKdteOZi25=zkRQrssO8xYw+iAWv8ub8OYQhrjQA0kfhHEcmzw@mail.gmail.com> (raw)
In-Reply-To: <504c2014-9764-c638-bf3a-0802132eb475@emrich-ebersheim.de>

On Tue, 16 Apr 2019 at 14:34, Rainer Emrich <rainer@emrich-ebersheim.de> wrote:
>
> Am 16.04.2019 um 14:10 schrieb Christophe Lyon:
> > On Tue, 16 Apr 2019 at 13:04, Rainer Emrich <rainer@emrich-ebersheim.de> wrote:
> >>
> >> Am 16.04.2019 um 11:59 schrieb Rainer Emrich:
> >>> Am 15.04.2019 um 20:12 schrieb Rainer Emrich:
> >>>> Am 15.04.2019 um 17:43 schrieb Rainer Emrich:
> >>>>> 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?
> >>>> The *.log.sep files seem to be ok.
> >>>>
> >>>>>> 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?
> >>>> I will try this over the night.
> >>> The shell version of dg-extract-results does not work either.
> >>>
> >>> AFAIS, there were changes to the dg-extract-results script 5th of March.
> >>> Looks like these changes are causing the issue, but I'm not sure.
> >>>
> >>> What I can say, my setup works at least for the gcc-8 branch and used to
> >>> work in the past.
> >> I tested dg-extractresults.sh manually and found that the change from
> >> 4th of February, revision 268411 broke the log extraction. Easy to test
> >> with version from 23rd of September last year which works.
> >>
> >> I don't have the time to analyze the python version, but my bet, it's
> >> the same issue.
> >>
> > Hi,
> >
> > Sorry for the breakage, I really wanted to improve those scripts.
> > Could you give me a reproducer, since we didn't notice problems in our
> > validations?
> Hi Christope,
>
> I executed the dg-extract-results.sh manually in the gcc/testsuite
> directory after a complete testsuite run which didn't give the correct
> results. Rev. 240429 gives the expected results, where rev 268511 fails.
> I'm on windows using msys2 with bash 4.4.23.
>
> I'm bootsrapping at the moment but that's really slow on windows. When
> the testsuite run is finished I try to assemble a reproducer. This will
> take a while.
>

OK, thanks! Do you mean the problem happens on Windows only?

> Thanks,
>
> Rainer
>

  reply	other threads:[~2019-04-16 12:49 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
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 [this message]
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='CAKdteOZi25=zkRQrssO8xYw+iAWv8ub8OYQhrjQA0kfhHEcmzw@mail.gmail.com' \
    --to=christophe.lyon@linaro.org \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=rainer@emrich-ebersheim.de \
    /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).