From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 92659 invoked by alias); 14 May 2015 23:41:05 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 92649 invoked by uid 89); 14 May 2015 23:41:05 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.3 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_PASS,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Thu, 14 May 2015 23:41:04 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id t4ENf0FP028236 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Thu, 14 May 2015 19:41:00 -0400 Received: from localhost (unused-10-15-17-126.yyz.redhat.com [10.15.17.126]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t4ENexIT031714 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA256 bits=256 verify=NO); Thu, 14 May 2015 19:41:00 -0400 From: Sergio Durigan Junior To: Don Breazeal Cc: "Breazeal\, Don" , "gdb-patches\@sourceware.org" Subject: Re: [pushed][PATCH 6/7] Extended-remote fork catch References: <1431451695-12273-1-git-send-email-donb@codesourcery.com> <1431451695-12273-6-git-send-email-donb@codesourcery.com> <87h9rehks0.fsf@redhat.com> <55552F17.3060807@codesourcery.com> X-URL: http://blog.sergiodj.net Date: Thu, 14 May 2015 23:41:00 -0000 In-Reply-To: <55552F17.3060807@codesourcery.com> (Don Breazeal's message of "Thu, 14 May 2015 16:26:15 -0700") Message-ID: <87y4kqg22f.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2015-05/txt/msg00372.txt.bz2 On Thursday, May 14 2015, Don Breazeal wrote: > The failures in gdb.base/foll-vfork.exp, gdb.base/multi-forks.exp, and > gdb.threads/fork-thread-pending.exp are not expected. Hey Dan, Well, because the GDB testsuite still has tests that fail intermitently, I was mostly talking about the failures on gdb.threads/fork-thread-pending.exp and gdb.base/foll-vfork.exp. > The failures in gdb.threads/interrupted-hand-call.exp and > gdb.gdb/python-selftest.exp are failures that I saw intermittently in my > testing, and was able to reproduce on the mainline, as discussed here: > https://sourceware.org/ml/gdb-patches/2015-05/msg00180.html Yeah, as Pedro already explained in this message, our testsuite is not entirely clean. But a "New FAIL", in general, means that a regression has been introduced. > The failure in gdb.base/attach.exp I don't know...the log doesn't > provide any clues. I'll have to reproduce it to understand it. Oh, this one is racy. But if you're interested in following this up, you can get the logs here: You have to choose the repository with the same name as the builder you saw the failure, and then, inside it, you can look for a git tag containing the commit hash (from the upstream GDB repo) that triggered the failure. Or, if you have the message from gdb-testers, you can see the direct link to the logs in the "Testsuite log (gdb.sum and gdb.log) URL(s):" field. > Disappointing. I'll check out a clean sandbox and see if I can > reproduce any of these results. Thanks for looking into this. As I said, I think the priority should be the new failures on gdb.threads/fork-thread-pending.exp and gdb.base/foll-vfork.exp. Cheers, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/