Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Edelsohn <dje.gcc@gmail.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: GDB 7.9.90 available for testing
Date: Fri, 10 Jul 2015 01:30:00 -0000	[thread overview]
Message-ID: <CAGWvnyn342DKXnOdh+un86NaZaQ6d-Dd+XdSfEK1nNn3+OhL6Q@mail.gmail.com> (raw)
In-Reply-To: <20150709232141.GA7406@adacore.com>

On Thu, Jul 9, 2015 at 7:21 PM, Joel Brobecker <brobecker@adacore.com> wrote:
>> Why should GDB 7.10 be considered ready for release with the large
>> number of regressions shown by the GDB Buildbot?  The buildbot only
>> recently was created and shows numerous regressions on almost all
>> architectures relative to when the buildslave started running.
>
> I don't follow the Buildbot day to day, unfortunately, and there are
> many configurations; so I rely on everyone with regular emails on
> this list to help me determine whether there might be issues blocking
> for (1) cutting the branch, and (2) making the official release.
> We keep the list on a wiki page that helps us track identified issues
> for each release.  For instance, for 7.10, we have:
>     https://sourceware.org/gdb/wiki/GDB_7.10_Release
> As you can see, very little has been reported.
>
> I am happy holding the creation of the official release up for
> however long it would take to analyze the buildBot failures,
> and to fix all blocking issues. Honestly, given the traffic seen
> here derived from issues found by the buildBot, I thought that
> people were already keeping an eye on the results.

I'm not certain if the baselines truly are accurate for all
buildslaves, but it seems strange to create a release when the
buildbot testsuite results show patches causing new failures.

- David


  reply	other threads:[~2015-07-10  1:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09 22:34 David Edelsohn
2015-07-09 23:21 ` Joel Brobecker
2015-07-10  1:30   ` David Edelsohn [this message]
2015-07-10  3:43     ` Joel Brobecker
2015-07-10 14:04       ` David Edelsohn
2015-07-10 14:33         ` Pedro Alves
2015-07-10 14:56           ` David Edelsohn
2015-07-10 15:08             ` Pedro Alves
2015-07-10 15:25               ` David Edelsohn
2015-07-10 15:33                 ` Pedro Alves
2015-07-11 13:59           ` Doug Evans
2015-07-11 18:54             ` racy tests Pedro Alves
2015-07-14 16:05               ` Doug Evans
2015-07-14 20:26               ` Sergio Durigan Junior
  -- strict thread matches above, loose matches on Subject: below --
2015-07-06 20:29 GDB 7.9.90 available for testing 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=CAGWvnyn342DKXnOdh+un86NaZaQ6d-Dd+XdSfEK1nNn3+OhL6Q@mail.gmail.com \
    --to=dje.gcc@gmail.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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