From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 90870 invoked by alias); 17 Jan 2020 15:36:28 -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 90861 invoked by uid 89); 17 Jan 2020 15:36:28 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-7.0 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_3,SPF_HELO_PASS,SPF_PASS,UNSUBSCRIBE_BODY autolearn=ham version=3.3.1 spammy=HX-Languages-Length:1606, emails, day X-HELO: simark.ca Received: from simark.ca (HELO simark.ca) (158.69.221.121) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 17 Jan 2020 15:36:18 +0000 Received: from [172.16.0.95] (192-222-181-218.qc.cable.ebox.net [192.222.181.218]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id EF6F81E47D; Fri, 17 Jan 2020 10:36:15 -0500 (EST) Subject: Re: Breakage on builder Fedora-x86_64-m64, revision 4814632e69636177b71b8d091009a0ec614916ec To: Jan Beulich , gdb-patches@sourceware.org, Sergio Durigan Junior References: <80b56bb1-ad16-7785-84c4-59f843791673@suse.com> From: Simon Marchi Message-ID: <04e45e46-f642-4c98-7a96-c67acd38b94f@simark.ca> Date: Fri, 17 Jan 2020 15:49:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: <80b56bb1-ad16-7785-84c4-59f843791673@suse.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2020-01/txt/msg00536.txt.bz2 On 2020-01-17 6:18 a.m., Jan Beulich wrote: > On 17.01.2020 11:41, gdb-buildbot@sergiodj.net wrote: >> Unfortunately it seems that there is a breakage on GDB. >> >> Commit title: 'x86: VPEXTRQ/VPINSRQ are unavailable outside of 64-bit mode' >> Revision: 4814632e69636177b71b8d091009a0ec614916ec >> >> You can find more details below: > > Unfortunately the details lack any details. This way I can neither put > it off, nor see about addressing it. > >> +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ >> >> >> +++ The full log is too big to be posted here. >> +++ These are the last 100 lines of it. > > I guess I can see why this is, but this way the only sign of a failures > is ... > >> make: *** [Makefile:853: all] Error 2 >> program finished with exit code 2 > > ... this. Hints as to what to do, or where to find the full build log, > appreciated. > > Jan > Sorry about that, that's not related to your patch. GDB's build was broken for a day. It is now fixed and I deleted most builds that I expect to fail, so we should not get too many more messages for this particular issue. That particular build was this one: https://gdb-buildbot.osci.io/#/builders/3/builds/1924 It would be nice if the emails included the URL to the specific build, so we could consult the full log. If that's not possible, then at least the URL to the home page of the buildbot and the build number separately would allow us to find the build relatively easily. But anyway, that's not your fault, sorry again for the noise. Simon