dg-extract-results broken since rev 268511, was Re: Status of 9.0.1 20190415 [trunk revision 270358] on x86_64-w64-mingw32

[Rainer Emrich <rainer at emrich-ebersheim dot de>]

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.

Attachment: signature.asc
Description: OpenPGP digital signature