From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 89546 invoked by alias); 16 Apr 2019 12:11:05 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 89533 invoked by uid 89); 16 Apr 2019 12:11:04 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-0.8 required=5.0 tests=AWL,BAYES_50,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no version=3.3.1 spammy=february, Emrich, emrich, February X-HELO: mail-ua1-f51.google.com Received: from mail-ua1-f51.google.com (HELO mail-ua1-f51.google.com) (209.85.222.51) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 16 Apr 2019 12:11:03 +0000 Received: by mail-ua1-f51.google.com with SMTP id c13so6617316uao.12 for ; Tue, 16 Apr 2019 05:11:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=LrfyqBf4jnbmW3zjUF6Bikq2Iq0JrvaqW1+qLNxkAx4=; b=RoACKgLWQNHw3CkbvLPbicxa8ht5R0PqBArgLg+iODj04wsnucGkrszgJ1Ov/8f6Im lfz+dRYt1fWyuz0x41BZ0tS9G9Q5JKrUSaXN1YigsyuHk9NHqY0DHW3CH+gjOJUZHLSy e4auKHwlr6nk4YEN1gTdyB5lXxNbXVqzOMUg5RoQaJ/LIBxp68RR8qDsxUeRzQa5sSs1 Gf6xtUUJjtmEnx6w4un3Ptm4XQAouI/d2dCWcloGScXPZRz6Kb+8cxF8+GjXMAcIdbF7 O0j4yK8my8XveCcYr0FjIDBw4n/ApeyM2ODJ4kP707FFV9YGo4ZRGLg2ylZbkCxk9xC8 zgyQ== MIME-Version: 1.0 References: <20190415153842.GU21066@tucnak> <34226dcf-24e4-370f-0f88-a69d979aef2e@emrich-ebersheim.de> <97c67265-af2a-b3f2-eecc-168abf4b5a6c@emrich-ebersheim.de> <8baf303a-9f01-15ec-7bbc-7b3419a96f00@emrich-ebersheim.de> <782fe033-0797-5574-0d62-af3ab4bf881e@emrich-ebersheim.de> In-Reply-To: <782fe033-0797-5574-0d62-af3ab4bf881e@emrich-ebersheim.de> From: Christophe Lyon Date: Tue, 16 Apr 2019 12:11:00 -0000 Message-ID: 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 To: Rainer Emrich Cc: Jakub Jelinek , gcc Mailing List , Christophe Lyon Linaro Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-04/txt/msg00169.txt.bz2 On Tue, 16 Apr 2019 at 13:04, Rainer Emrich 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? Thanks, Christophe