public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: GDB Development <gdb@sourceware.org>
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Re: [ANNOUNCEMENT] GDB BuildBot
Date: Wed, 21 Jan 2015 22:53:00 -0000	[thread overview]
Message-ID: <87lhkvd9u7.fsf@redhat.com> (raw)
In-Reply-To: <87bnm1exo6.fsf@redhat.com> (Sergio Durigan Junior's message of	"Wed, 14 Jan 2015 18:43:05 -0500")

On Wednesday, January 14 2015, I wrote:

> Hi all,
>
> It took a bit more time than I was planning, but finally I am back to
> announce our BuildBot.  I really expect that it will help us improve our
> codebase and catch regressions/failures sooner (in fact, it already
> helped me to catch at least 2 regressions).

Hey guys,

It's been a week since our BuildBot is running, and I would like to
say/ask a few things.

First, thanks to Mark Wielaard for setting up a Debian Wheezy x86_64
machine as one of our buildslaves!  And also, thanks for Tulio Magno and
for IBM/UNICAMP for providing a PPC64LE VM where I could set up another
buildslave for us.  So now, GDB is being tested on:

- Fedora 21 x86_64
- Debian Wheezy x86_64
- Fedora 21 ppc64le

Not bad for a first week :-).  I also plan to set up a buildslave for us
on an AIX machine from the GCC Farm (thanks to David Edelsohn for the
reminder).

Now, the questions.

1) I am still tweaking the notifications that are sent to the
gdb-testers mailing list.  Do you have any ideas/suggestions for
improvement?

2) Are you guys actually seeing the notifications that are sent to the
gdb-testers?  :-).  I know the amount of e-mails can get annoying, and
that's why I'm trying to reduce them by tracking the XFAIL's, but I'd
like to know if this is being used.

3) Eli requested, and I created a new "make TAGS" pass that is performed
on every build.  It is failing every time now (because of the some
issues found by Eli and posted to the gdb-patches).  I could make
BuildBot generate an e-mail for every failure, but this would massively
increase the number of e-mails sent to the gdb-testers.  So, for now, I
am only sending an e-mail *if* some regression has been found.  Is it OK
for you?  Would you like me to make BuildBot send an e-mail every time
"make TAGS" fail?

Other than that, I think we our BuildBot is looking good, and we will
soon be able to filter the noise and catch only the real regressions.
Meanwhile, if you want to help, you can:

- Help me filter the XFAIL tests

- Contribute with a buildslave!

- Improve the current configuration, which can be found (temporarily) at
  <http://git.sergiodj.net/?p=gdb-buildbot.git;a=summary>.

Cheers,

-- 
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/

  parent reply	other threads:[~2015-01-21 22:53 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-14 23:43 Sergio Durigan Junior
2015-01-15 12:13 ` Joel Brobecker
2015-01-15 19:36   ` Sergio Durigan Junior
2015-01-21 22:53 ` Sergio Durigan Junior [this message]
2015-01-22 18:15   ` Eli Zaretskii
2015-01-22 18:38     ` Sergio Durigan Junior
2015-01-22 18:43       ` Eli Zaretskii
2015-01-22 18:57         ` Sergio Durigan Junior
2015-01-22 19:25           ` Eli Zaretskii
2015-01-22 19:55             ` Eli Zaretskii
2015-01-22 20:32             ` Sergio Durigan Junior
2015-01-22 20:39               ` Eli Zaretskii
2015-01-22 20:48                 ` Eli Zaretskii
2015-01-22 21:32                   ` Eli Zaretskii
2015-01-22 22:28                     ` Sergio Durigan Junior
2015-01-22 22:34                       ` Doug Evans
2015-01-23  9:06                         ` Sergio Durigan Junior
2015-01-23  9:57                           ` Eli Zaretskii
2015-01-23  9:09                       ` Eli Zaretskii
2015-01-23 10:14                         ` Pedro Alves
2015-01-23 11:01                           ` Eli Zaretskii
2015-01-23 16:16                     ` Andreas Schwab
2015-01-23 17:47                       ` Eli Zaretskii
2015-01-22 21:46                   ` Sergio Durigan Junior
2015-01-23 10:41             ` Pedro Alves
2015-01-23 10:46               ` Eli Zaretskii
2015-01-23 14:25                 ` Pedro Alves
2015-01-27 16:42   ` Mark Wielaard
2015-01-27 20:05     ` Sergio Durigan Junior

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=87lhkvd9u7.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).