This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: GDB 7.10 release 2015-07-17 status update?
- From: Sergio Durigan Junior <sergiodj at redhat dot com>
- To: Joel Brobecker <brobecker at adacore dot com>
- Cc: gdb-patches at sourceware dot org, keiths at redhat dot com, Jan Kratochvil <jan dot kratochvil at redhat dot com>
- Date: Fri, 17 Jul 2015 16:24:50 -0400
- Subject: Re: GDB 7.10 release 2015-07-17 status update?
- Authentication-results: sourceware.org; auth=none
- References: <20150717175328 dot GA15874 at adacore dot com>
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/