From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 116214 invoked by alias); 28 Feb 2018 12:00:56 -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 115213 invoked by uid 89); 28 Feb 2018 12:00:55 -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,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=hrs X-HELO: mail-pf0-f174.google.com Received: from mail-pf0-f174.google.com (HELO mail-pf0-f174.google.com) (209.85.192.174) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 28 Feb 2018 12:00:53 +0000 Received: by mail-pf0-f174.google.com with SMTP id q13so901226pff.0 for ; Wed, 28 Feb 2018 04:00:53 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-transfer-encoding; bh=vz6SYsc7YzjFEwHwfJUwFlXz9cLVvq3hQp3NT7/HPCQ=; b=TsXs8F1F0Pf/+tPx321t1Xrbvl0kr4RQFbiDlj+O4Ipglhbt9c9oDZr8Pqca3nLMBY yc8KHE2Z9GvAwg9VRD1zFYSq15MH5lMspyzgzDndiCNfHmp6USkrvTlc2fLCYnEEFDQo 7ThU88TPuUVNa9lCf2l06TQoJ0MaejHwRaAE2FBXoJJq4E71amW6vJbiU+k/o21rJPYt M4Qz28Pe3/VXjZqTrRGKdIvnRXE3xLgQSQjiboHdR5FxpryWHXZVEn4VvHAKq+LHvv26 lut+Cg3LzQovCjECETu3zO8BpiQbw/UlFN49xBa5gRXOYELxiTu+gdUCm63mzF+4YjHX 1+Ig== X-Gm-Message-State: APf1xPCCu5Yxzn8TFCHUrjsLQmiBIm6W2jYm0PeGuwIjdqkBVKes4mrs LeDNM5AB4ivBQo2w1T2n20JWUQ== X-Google-Smtp-Source: AH8x226HfPjBHfzz8qWZxdVEZx3hNywLdBFxBnlV4bXwhB/GDGpNKdhZK1M6Tojc9UqkwqZ22DZIcA== X-Received: by 10.101.93.71 with SMTP id e7mr14312001pgt.248.1519819252369; Wed, 28 Feb 2018 04:00:52 -0800 (PST) Received: from E107787-LIN (gcc114.osuosl.org. [140.211.9.72]) by smtp.gmail.com with ESMTPSA id e22sm2788291pgn.50.2018.02.28.04.00.50 (version=TLS1_2 cipher=AES128-SHA bits=128/128); Wed, 28 Feb 2018 04:00:51 -0800 (PST) From: Yao Qi To: "Maciej W. Rozycki" Cc: Markus Metzger , , sergiodj@redhat.com Subject: Re: [PATCH v2 5/7] btrace, gdbserver: remove the to_supports_btrace target method References: <1516976072-19282-1-git-send-email-markus.t.metzger@intel.com> <1516976072-19282-6-git-send-email-markus.t.metzger@intel.com> Date: Wed, 28 Feb 2018 12:00:00 -0000 In-Reply-To: (Maciej W. Rozycki's message of "Sat, 24 Feb 2018 16:31:42 +0000") Message-ID: <86woyxgw7l.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2018-02/txt/msg00456.txt.bz2 "Maciej W. Rozycki" writes: > Hmm, v3 of this change (apparently never posted), that is specifically=20 > commit de6242d30757 ("btrace, gdbserver: remove the to_supports_btrace=20 > target method"), has broken remote `mips-linux' target debugging=20 > completely, that is an attempt to make a remote connection fails in the=20 > initial handshake, e.g.: > > Process .../gdb/testsuite/outputs/gdb.base/advance/advance created; pid = =3D 25519 > Listening on port 2346 > target remote 1.2.3.4:2346 > Remote debugging using 1.2.3.4:2346 > Reading symbols from .../lib/ld.so.1...done. > 0x77fc8de0 in __start () from .../lib/ld.so.1 > Protocol error: qXfer:btrace-conf (read-btrace-conf) conflicting enabled = responses. > (gdb) continue > The program is not being run. > (gdb) FAIL: gdb.base/advance.exp: can't run to main For the record, since non-x86 gdbserver is broken, it takes much longer to run gdb tests on non-x86 gdbserver buildbot builders, On Ubuntu-AArch64-native-gdbserver-m64, the time is changed from 17 mins to 5 hrs 50 mins;=20 https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-native-gdbserver-m64= /builds/4141 On CentOS-ppc64be-native-gdbserver-m64, the time is changed from 48 mins to 6 hrs 34 mins; https://gdb-build.sergiodj.net/builders/CentOS-ppc64be-native-gdbserver-m64= /builds/155 CentOS-ppc64le-native-gdbserver-m64, Fedora-ppc64le-native-gdbserver-m64 and Debian-s390x-native-gdbserver-m64 are affected as well. By the time Markus's fix is pushed in, these builders can run tests for only 4 commits every day, and there are already 184 commits pushed after commit de6242d30757. It takes at least 46 days to build and test every commit. If we take "try" jobs submitted in the last several days into account, it takes more time to clear the queue. Sergio, in short, non-x86 gdbserver is broken, it takes several hours to run gdb tests with gdbserver builders. As a result, many builds are pending there, and it still also takes much time to clean them up. After Markus commit his fix, can we do something to let non-x86 gdbserver builders to skip these pending builds, and "jump" to Markus's fix? Or can we temporarily disable non-x86 builders, restart them after the fix is committed, and make sure builders pick the most recent commit rather than resuming from the pending builds. --=20 Yao (=E9=BD=90=E5=B0=A7)