Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: --enable-build-with-cxx buildslave?
Date: Fri, 15 May 2015 18:39:00 -0000	[thread overview]
Message-ID: <87h9rdelc9.fsf@redhat.com> (raw)
In-Reply-To: <55562822.7060703@redhat.com> (Pedro Alves's message of "Fri, 15	May 2015 18:08:50 +0100")

On Friday, May 15 2015, Pedro Alves wrote:

>> Hm, we're kind of running short on resources to add new builders there,
>> but I can try to squeeze one more using the x86_64 buildslave I have
>> here.  I'll give it a try today and see if the machine can handle the
>> load, and then I'll let you know.
>
> I'd be happy with making it only do the build steps, to catch build
> regressions.  We can worry about enabling the testsuite after we're
> done getting rid of -fpermissive.

OK, that is easier :-).  I set the thing up.  You can see the builder
here:

  <http://gdb-build.sergiodj.net/builders/Fedora-x86_64-cxx-build-m64>

It is not running the testsuite, so it won't generate e-mail
notifications to the gdb-testers mailing list *unless* something really
important happens, which is exactly what you asked :-).  The good thing
is that we won't need to worry about racy tests for this one!

I'll monitor it to see if it works OK for the first builds.  If you see
anything wrong there, just let me know.

Cheers,

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


  reply	other threads:[~2015-05-15 18:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 15:24 Pedro Alves
2015-05-15 16:58 ` Sergio Durigan Junior
2015-05-15 17:08   ` Pedro Alves
2015-05-15 18:39     ` Sergio Durigan Junior [this message]
2015-05-15 18:42       ` Pedro Alves

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=87h9rdelc9.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    /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