Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Brendan Kirby <brendan.kirby@imgtec.com>
Cc: <gdb@sourceware.org>
Subject: Re: MIPS GDB Buildbot slave running Debian Jessie
Date: Mon, 13 Jul 2015 23:13:00 -0000	[thread overview]
Message-ID: <87bnffbqin.fsf@redhat.com> (raw)
In-Reply-To: <55A42E63.9000004@imgtec.com> (Brendan Kirby's message of "Mon,	13 Jul 2015 14:32:19 -0700")

On Monday, July 13 2015, Brendan Kirby wrote:

> I'm interested in setting up a GDB Buildbot slave on a MIPS board.  The
> board is an Edge Router Pro board running Debian Jessie. I've
> configured, built and run the GDB test suite on it based on the steps
> other builders are using in the GDB Buildbot master.  Due to what looks
> like I-cache coherency issues in the kernel the board needs to be run
> with no SMP.  Otherwise it builds and runs the test suite correctly. 
> We're passing over 23,000 of the GDB tests, but we still have 400 to 500
> test failures.  Would it be possible to get this board added to the GDB
> Buildbot?  If so, could you send me or point me at the config.json and
> the master.cfg files so that I can send a patch?

Hi Brendan,

Yes, your MIPS buildslave would be very welcome to our BuildBot!  In
order to simplify things, you can send me an e-mail offlist with the
following information:

- name of the buildslave;

- how many jobs it can handle when compiling/testing (i.e., what is the
  value of N in "make -j<N>")

- what types of builders do you want to assign to it (I suppose it will
  just build the plain GDB, i.e., no
  native-gdbserver/native-extended-gdbserver)

- the admin's e-mail address (BuildBot will send an e-mail to this
  address if the slave gets disconnected)

Also, don't forget to edit the "config/{info,host}" files (under your
buildslave directory) and put useful information there (take a look at
the "Slave information" section on any buildslave page to see examples).

After I have everything, I will generate a password for the slave and
send it to you, and you will be able to connect it to our BuildBot.

Thanks for the offer!

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


  parent reply	other threads:[~2015-07-13 23:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-13 21:32 Brendan Kirby
2015-07-13 21:55 ` pinskia
2015-07-13 23:01   ` Brendan Kirby
2015-07-13 23:13 ` Sergio Durigan Junior [this message]
2015-07-14 17:37 ` 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=87bnffbqin.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=brendan.kirby@imgtec.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