From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: GDB Development <gdb@sourceware.org>
Subject: Re: [ANNOUNCEMENT] GDB BuildBot
Date: Thu, 15 Jan 2015 19:36:00 -0000 [thread overview]
Message-ID: <87oapzbzuw.fsf@redhat.com> (raw)
In-Reply-To: <20150115121259.GC28195@adacore.com> (Joel Brobecker's message of "Thu, 15 Jan 2015 16:12:59 +0400")
On Thursday, January 15 2015, Joel Brobecker wrote:
> Hi Sergio,
Hey Joel,
>> 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).
>>
>> The initial idea was to deploy our BuildBot master directly on
>> sourceware, but unfortunately this was not possible. So, after trying
>> to find other places, I decided to use my own personal server. However,
>> my main goal is to turn this project into something official for the GDB
>> project, and I do hope that using my own server does not give a false
>> sense of "this is Sergio's pet-project".
>>
>> Having said that, the current address for our BuildBot is:
>>
>> <http://gdb-build.sergiodj.net/>
>
> I started taking a look, and this looks very very nice.
> The interface already looks quite sleek and polished!
Thank you :-).
> We've all already seen that the bot help us a couple of times
> associate regressions with specific commits, so I know it's going
> to be really useful, and I look forward to more reports (actually,
> not really, but that wouldn't be the bot's fault ;-)).
Great! I am seeing some fuzzy test results there now, so it will take
some time until everything is set up perfectly. But, baby steps!
> Perhaps you might want to present it and give a demo at the next
> GNU Cauldron :-)...
It would be neat :-). I just have to be able to attend the conference
:-P.
Cheers,
--
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2015-01-15 19:36 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 [this message]
2015-01-21 22:53 ` Sergio Durigan Junior
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=87oapzbzuw.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=brobecker@adacore.com \
--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