From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 56197 invoked by alias); 1 Mar 2016 05:58:55 -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 56187 invoked by uid 89); 1 Mar 2016 05:58:54 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=month, our 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; Tue, 01 Mar 2016 05:58:53 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (Postfix) with ESMTPS id A3A9F7AE80; Tue, 1 Mar 2016 05:58:52 +0000 (UTC) Received: from localhost (unused-10-15-17-51.yyz.redhat.com [10.15.17.51]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u215wpqa017724 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 1 Mar 2016 00:58:52 -0500 From: Sergio Durigan Junior To: Antoine Tremblay Cc: GDB Patches Subject: Re: [PATCH] Improve analysis of racy testcases References: <87r3gcgm91.fsf@redhat.com> X-URL: http://blog.sergiodj.net Date: Tue, 01 Mar 2016 05:58:00 -0000 In-Reply-To: (Antoine Tremblay's message of "Thu, 25 Feb 2016 13:33:56 -0500") Message-ID: <878u22wxgk.fsf@redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-IsSubscribed: yes X-SW-Source: 2016-03/txt/msg00001.txt.bz2 On Thursday, February 25 2016, Antoine Tremblay wrote: > Sergio Durigan Junior writes: > >> This patch is a proposal to introduce some mechanisms to identify racy >> testcases present in our testsuite. As can be seen in previous >> discussions, racy tests are really bothersome and cause our BuildBot to >> pollute the gdb-testers mailing list with hundreds of false-positives >> messages every month. Hopefully, by identifying these racy tests in >> advance (and automatically) will contribute to the reduction of noise >> traffic to gdb-testers, maybe to the point where we will be able to send >> the failure messages directly to the authors of the commits. >> [...] > Thanks for this ! This was quite a problem for me while testing on arm. > I'm testing it now... Thanks! Please let me know if you find anything wrong with the script. > One note maybe it would be nice output the list of unracy tests too to > be able to auto-build a list of tests to run out of this since I'm not > sure you can set an exclusion list ? Hm, it would be possible to output the non-racy tests, but only to a different file (instead of outputting to stdout, as I'm doing with the racy tests). Perhaps this could be a separate option to the script? I'm not sure if the users would always want this information... As for the exclusion list you mentioned, DejaGNU's runtest allows one to specify a --ignore flag with the names of the tests you don't want to run. It should be possible to pass this via RUNTESTFLAGS, but I haven't tried. I'll give it a go tomorrow. 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/