Re: RFC: branching for GDB 7.11 soon? (possibly Wed)

[Sergio Durigan Junior <sergiodj@redhat.com>]

On Tuesday, February 09 2016, Simon Marchi wrote:

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

Hm, recently some extra packages were installed on some buildslaves in
order to test more things; one of those packages was gcc-gnat for Ada.
I think that may indeed be the cause.  Sorry if that was a false alarm.

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

These tests don't seem to be racy, so if you can't reproduce the
failures, I'd say you did not introduce them.

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/