From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>, Yao Qi <qiyaoltc@gmail.com>
Cc: "Maciej W. Rozycki" <macro@mips.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH v2 5/7] btrace, gdbserver: remove the to_supports_btrace target method
Date: Thu, 01 Mar 2018 11:33:00 -0000 [thread overview]
Message-ID: <A78C989F6D9628469189715575E55B236964E6E1@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <87o9k9m651.fsf@redhat.com>
Hello Sergio,
> What I can do is manually cancel all the build until Markus's commit.
> I've done that before for other builders, so it is possible.
I pushed the fix.
I'm sorry about the breakage this caused and the lost test coverage for
the commits for which we will have to cancel testing.
Thanks for helping with buildbot, Sergio.
Regards,
Markus.
> -----Original Message-----
> From: Sergio Durigan Junior [mailto:sergiodj@redhat.com]
> Sent: 28 February 2018 17:27
> To: Yao Qi <qiyaoltc@gmail.com>
> Cc: Maciej W. Rozycki <macro@mips.com>; Metzger, Markus T
> <markus.t.metzger@intel.com>; gdb-patches@sourceware.org
> Subject: Re: [PATCH v2 5/7] btrace, gdbserver: remove the to_supports_btrace
> target method
>
> On Wednesday, February 28 2018, Yao Qi wrote:
>
> > "Maciej W. Rozycki" <macro@mips.com> writes:
> >
> >> Hmm, v3 of this change (apparently never posted), that is
> >> specifically commit de6242d30757 ("btrace, gdbserver: remove the
> >> to_supports_btrace target method"), has broken remote `mips-linux'
> >> target debugging completely, that is an attempt to make a remote
> >> connection fails in the initial handshake, e.g.:
> >>
> >> Process .../gdb/testsuite/outputs/gdb.base/advance/advance created;
> >> pid = 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;
> > https://gdb-build.sergiodj.net/builders/Ubuntu-AArch64-native-gdbserve
> > r-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-gdbserve
> > r-m64/builds/155
> >
> > CentOS-ppc64le-native-gdbserver-m64,
> > Fedora-ppc64le-native-gdbserver-m64 and
> > Debian-s390x-native-gdbserver-m64 are affected as well.
>
> Ah, that explains the failures I am seeing.
>
> > 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.
>
> What I can do is manually cancel all the build until Markus's commit.
> I've done that before for other builders, so it is possible.
>
> I'll keep an eye and do that when the commit is pushed. Thanks for keeping me
> in the loop, Yao.
>
> --
> Sergio
> GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send
> encrypted e-mail if possible http://sergiodj.net/
Intel Deutschland GmbH
Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de
Managing Directors: Christin Eisenschmid, Christian Lamprechter
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2018-03-01 11:33 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-26 14:14 [PATCH v2 0/7] improve btrace enable error reporting Markus Metzger
2018-01-26 14:14 ` [PATCH v2 6/7] btrace: improve enable error messages Markus Metzger
2018-01-26 14:14 ` [PATCH v2 4/7] btrace, gdbserver: use exceptions to convey btrace enable/disable errors Markus Metzger
2018-01-26 14:14 ` [PATCH v2 2/7] common: add scoped_mmap Markus Metzger
2018-01-26 14:14 ` [PATCH v2 1/7] common: add scoped_fd Markus Metzger
2018-02-13 16:48 ` Yao Qi
2018-02-13 17:28 ` Metzger, Markus T
2018-02-14 15:22 ` Yao Qi
2018-02-14 17:26 ` Metzger, Markus T
2018-02-19 15:28 ` Metzger, Markus T
2018-02-20 10:12 ` Yao Qi
2018-02-20 10:46 ` Metzger, Markus T
2018-01-26 14:14 ` [PATCH v2 5/7] btrace, gdbserver: remove the to_supports_btrace target method Markus Metzger
2018-02-24 16:51 ` Maciej W. Rozycki
2018-02-26 13:08 ` Metzger, Markus T
2018-02-26 19:30 ` Andreas Arnez
2018-02-26 21:58 ` Maciej W. Rozycki
2018-02-27 10:57 ` Metzger, Markus T
2018-02-27 15:32 ` Maciej W. Rozycki
2018-02-27 18:14 ` Metzger, Markus T
2018-02-28 10:29 ` Maciej W. Rozycki
2018-02-28 11:09 ` Maciej W. Rozycki
2018-02-28 11:24 ` Metzger, Markus T
2018-02-28 12:53 ` Metzger, Markus T
2018-02-28 15:55 ` Maciej W. Rozycki
2018-02-28 16:08 ` Eli Zaretskii
2018-02-28 12:00 ` Yao Qi
2018-02-28 16:27 ` Sergio Durigan Junior
2018-03-01 11:33 ` Metzger, Markus T [this message]
2018-03-01 19:27 ` Sergio Durigan Junior
2018-03-05 12:14 ` Yao Qi
[not found] ` <87lgf64i24.fsf@redhat.com>
2018-03-06 9:02 ` Yao Qi
2018-03-06 16:32 ` Sergio Durigan Junior
2018-03-01 19:34 ` Maciej W. Rozycki
2018-01-26 14:14 ` [PATCH v2 3/7] btrace: prepare for throwing exceptions when enabling btrace Markus Metzger
2018-02-06 16:28 ` [PATCH v2 0/7] improve btrace enable error reporting Pedro Alves
2018-02-07 10:41 ` Metzger, Markus T
2018-02-07 12:11 ` Pedro Alves
2018-02-08 10:40 ` Metzger, Markus T
[not found] ` <9ce0c90a-5c71-0a7d-3779-f826369a95ec@redhat.com>
2018-02-08 13:49 ` Metzger, Markus T
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A78C989F6D9628469189715575E55B236964E6E1@IRSMSX104.ger.corp.intel.com \
--to=markus.t.metzger@intel.com \
--cc=gdb-patches@sourceware.org \
--cc=macro@mips.com \
--cc=qiyaoltc@gmail.com \
--cc=sergiodj@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox