Am 16.04.2019 um 14:49 schrieb Christophe Lyon:
> On Tue, 16 Apr 2019 at 14:34, Rainer Emrich <rai...@emrich-ebersheim.de>
> wrote:
>>
>> Am 16.04.2019 um 14:10 schrieb Christophe Lyon:
>>> On Tue, 16 Apr 2019 at 13:04, Rainer Emrich <rai...@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?
I don't know at the moment, because im only bootstrapping and testing on
windows on a semi regular basis. AFAIK I'm the only person which is
doing semi regular testsuite runs on windows and pushing the results to
gcc-testresults mailing list.I doubt that I will find the time for bootstrapping and running the testsuite on linux in the next few days.
signature.asc
Description: OpenPGP digital signature
