This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: RFC: branching for GDB 7.11 soon? (possibly Wed)
- From: Simon Marchi <simon dot marchi at ericsson dot com>
- To: Pedro Alves <palves at redhat dot com>, Sergio Durigan Junior <sergiodj at redhat dot com>, Joel Brobecker <brobecker at adacore dot com>
- Cc: <gdb-patches at sourceware dot org>, <keiths at redhat dot com>
- Date: Tue, 9 Feb 2016 09:52:36 -0500
- Subject: Re: RFC: branching for GDB 7.11 soon? (possibly Wed)
- Authentication-results: sourceware.org; auth=none
- References: <20160201030638 dot GG4008 at adacore dot com> <20160207081230 dot GA20874 at adacore dot com> <87mvrajviz dot fsf at redhat dot com> <56B9F460 dot 7080404 at ericsson dot com> <56B9F53A dot 7020305 at redhat dot com>
On 16-02-09 09:18 AM, Pedro Alves wrote:
> On 02/09/2016 02:14 PM, Simon Marchi wrote:
>> On 16-02-09 12:35 AM, Sergio Durigan Junior wrote:
>>> Today, Simon pushed a commit that caused a few regressions on Ada, on
>>> some builders. This is:
>>>
>>> <https://sourceware.org/ml/gdb-testers/2016-q1/msg04420.html>
>>
>> I'll look into it right now. I did not receive anything from the
>> buildbot, is it normal?
>
> Yes, only build breakages get you a nag email. "Normal" testsuite
> regressions don't result in personal notifications, because the testsuite
> still trips on too many racy failures. Once the testing infrustructure handles
> racy tests more gracefully, and testing is more stable, I think we should
> enable personal nags, but not yet.
Ok, my understanding was that I broke some previously passing tests. Upon
inspection, it seems like before my commit, a lot of Ada tests simply were
not running. For example:
FAIL: gdb.ada/aliased_array.exp: compilation foo.adb
becomes
PASS: gdb.ada/aliased_array.exp: compilation foo.adb
FAIL: gdb.ada/aliased_array.exp: print bt
Which introduces new FAILs. But there is no previously passing test that
now fails, I think. So if that's the case, I don't think it should block
the release.
Also, I don't have all those failures when I run the testsuite on my machine,
so I don't really know what causes them.