Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org,  keiths@redhat.com,
	 Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: GDB 7.10 release 2015-07-17 status update?
Date: Mon, 20 Jul 2015 10:06:00 -0000	[thread overview]
Message-ID: <86io9fi1op.fsf@gmail.com> (raw)
In-Reply-To: <20150717175328.GA15874@adacore.com> (Joel Brobecker's message of	"Fri, 17 Jul 2015 10:53:28 -0700")

Joel Brobecker <brobecker@adacore.com> writes:

> 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.

Yes, I looked at them last week.  I can't reproduce most of them on my
machine.  For fails I can reproduce, I identified the patches related to
these fails, and ping the authors.

  - fails in gdb.arch/i386-biarch-core.exp are fixed by Jan
  https://sourceware.org/ml/gdb-patches/2015-07/msg00476.html

  - GDBserver crashes when killing a multi-thread process.  Remind Pedro
  to commit his patch.
  https://sourceware.org/ml/gdb-patches/2015-03/msg00182.html

  - fails in attach-pie-noexec.exp fail on native-extended-gdbserver are
    fixed by me.
  https://sourceware.org/ml/gdb-patches/2015-07/msg00367.html

  - fails in gdb.base/gnu_vector.exp are being discussed.
  https://sourceware.org/ml/gdb-patches/2015-07/msg00315.html
  These fails are not fixed, but they are test case problem rather than
  GDB's problem.  I still don't have a chance to think about how to make
  different architectures/os happy for this test case.  IMO, these fails
  shouldn't block 7.10 release.

  - fails in gdb.server/wrapper.exp
  I am working on a patch series to fix these fails, and probably I'll
  send them out today or tomorrow.
  I'd like to fix it before 7.10 release.

-- 
Yao (齐尧)


  parent reply	other threads:[~2015-07-20 10:06 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-17 17:53 Joel Brobecker
2015-07-17 18:14 ` Luis Machado
2015-07-17 18:32   ` Joel Brobecker
2015-07-17 18:38     ` Luis Machado
2015-07-17 19:06       ` Eli Zaretskii
2015-07-17 20:48       ` Joel Brobecker
2015-07-17 20:57         ` Luis Machado
2015-07-20 10:13       ` Iain Buclaw
2015-07-21 17:16         ` Joel Brobecker
2015-07-17 19:04     ` Eli Zaretskii
2015-07-17 19:03   ` Eli Zaretskii
2015-07-24  9:26     ` Pedro Alves
2015-07-24 14:31       ` Iain Buclaw
2015-07-24 14:37         ` Pedro Alves
2015-07-17 18:25 ` Keith Seitz
2015-07-17 18:28 ` Jan Kratochvil
2015-07-17 18:35   ` Joel Brobecker
2015-07-17 20:15 ` Simon Marchi
2015-07-17 20:57   ` Joel Brobecker
2015-07-17 21:00     ` Simon Marchi
2015-07-17 20:24 ` Sergio Durigan Junior
2015-07-20 10:06 ` Yao Qi [this message]
2015-07-21 17:11   ` Joel Brobecker

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=86io9fi1op.fsf@gmail.com \
    --to=qiyaoltc@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=keiths@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