From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 41669 invoked by alias); 17 Jul 2015 20:24: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 41654 invoked by uid 89); 17 Jul 2015 20:24:53 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham 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; Fri, 17 Jul 2015 20:24:52 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (Postfix) with ESMTPS id 756564D; Fri, 17 Jul 2015 20:24:51 +0000 (UTC) Received: from localhost (unused-10-15-17-51.yyz.redhat.com [10.15.17.51]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id t6HKOoNL005108 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 17 Jul 2015 16:24:51 -0400 From: Sergio Durigan Junior To: Joel Brobecker Cc: gdb-patches@sourceware.org, keiths@redhat.com, Jan Kratochvil Subject: Re: GDB 7.10 release 2015-07-17 status update? References: <20150717175328.GA15874@adacore.com> X-URL: http://blog.sergiodj.net Date: Fri, 17 Jul 2015 20:24:00 -0000 In-Reply-To: <20150717175328.GA15874@adacore.com> (Joel Brobecker's message of "Fri, 17 Jul 2015 10:53:28 -0700") Message-ID: <87fv4mttv1.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: 2015-07/txt/msg00523.txt.bz2 On Friday, July 17 2015, Joel Brobecker wrote: > David Edelson reported that the buildBot was reporting a lot of > failures around the time we cut the branch. Has anyone looked at those > since then? When I did, I was looking at the waterfall view, and > several builds looked like they were failing right at the beginning, > so I didn't know what to make of it. Also, that's a lot of info to > grok, so I didn't have time to look further. > > What I can say is that I've tested the branch with a number of > platforms, not as exhaustively of course, but so far, it looks > pretty good. Heya, As has been explained before, our testsuite contains some racy tests, and therefore our BuildBot is just spilling lots of FAIL's from them. I have been trying to work on a solution to help address this problem; meanwhile, other are looking at the logs (mostly Yao, I think) and reporting whenever they see something there. > What I think we should do is give it another couple of weeks, and > see if other reports come up. It would be good, also, if we had > some info about the buildBOT failures, and whether the release > might be affected by any regression it found. Yeah, I agree. I'll investigate the logs and see if they contain something suspicious. Unfortunately, due to the recent problem (reported at ) the build logs are not available anymore for a number of builds... But the BuildBot logs (i.e., the e-mails it sends to gdb-testers -- those have not been affected) should be enough to determine if there's something strange. Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/