public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.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: Fri, 17 Jul 2015 20:24:00 -0000	[thread overview]
Message-ID: <87fv4mttv1.fsf@redhat.com> (raw)
In-Reply-To: <20150717175328.GA15874@adacore.com> (Joel Brobecker's message of	"Fri, 17 Jul 2015 10:53:28 -0700")

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
<https://sourceware.org/ml/gdb-patches/2015-07/msg00506.html>) 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/

  parent reply	other threads:[~2015-07-17 20:24 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 [this message]
2015-07-20 10:06 ` Yao Qi
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=87fv4mttv1.fsf@redhat.com \
    --to=sergiodj@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).