public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Provide Solaris 11 buildbots
Date: Wed, 19 Sep 2018 19:46:00 -0000	[thread overview]
Message-ID: <874lelw9r3.fsf@redhat.com> (raw)
In-Reply-To: <ydda7odk9ye.fsf@CeBiTec.Uni-Bielefeld.DE> (Rainer Orth's message	of "Wed, 19 Sep 2018 13:23:05 +0200")

On Wednesday, September 19 2018, Rainer Orth wrote:

> If the proposed Solaris 11 buildbots
>
> 	https://sourceware.org/ml/gdb/2018-09/msg00004.html

Thanks for the offer, and for the patch!

IMO, "the more the merrier".  So yeah, Solaris 11 buildslaves are
absolutely welcome.

> are considered worthwhile, here's a patch to introduce them.  It's
> completely untested of course (I cannot even check syntactic validity),
> and there are a couple of caveats:
>
> * While a regular gdb build succeeds, a -g -D_GLIBCXX_DEBUG build as
>   used by the buildbot fails as reported in PR build/23676.  This can be
>   avoided either by performing a -g -O build or with
>   --disable-unit-tests from Sergio's proposed patch.

Oh, cool, I saw your comment regarding my patch on the bug.  I'm happy
it helps to solve other problems.

> * The buildslaves are configured to be compile-only at the moment: at
>   -j4, a build takes ca. 15 minutes, while make check takes 1h 15 due to
>   many timeouts (mostly in gdb.threads).  Until those are resolved, it's
>   probably useless to run the tests.

Right.  Until I implement a way to enable only a subset of tests from
our testsuite, I agree that it's not a good idea to have builds taking
that long to finish.

> * I couldn't find proper documentation for at least two fields:
>
> ** arch in config.json (slaves), seems to be unused AFAICT
>
> ** tags in config.json (builders)

Sorry about that.

The "arch" field is indeed unused.  The initial plan was to use it to
offer some filtering capabilities in the web interface, but that's been
replaced by "tags".

The "tags" filter is just a collection of tags that are used to
categorize the builders.  If you go to
<https://gdb-build.sergiodj.net/waterfall>, at the top of the page
you'll see a "Tags:" header, with a bunch of tags.  You can use them to
selectively display just the builders associated with a certain tag.
For example, if you want to list the x86_64 builders, you'd go to
<https://gdb-build.sergiodj.net/waterfall?tag=x86_64>.

There are two "special" tags: "MAIL" and "TEST".  When a builder is
marked as "MAIL", the BuildBot master will send e-mail notifications
about it to gdb-testers/gdb-patches.  If it's marked as "TEST", then all
e-mail notifications are supressed.  I just mark a builder as "TEST" if
it proves to unstable (i.e., when GDB fails to compile on it because of
some problem with the builder itself).  I think it makes sense to mark
your builders as "MAIL", since they're relatively stable, from what you
said.

I'll have to contact you in private in order to give the password
necessary for connection to the BuildBot master.  I'll also apply your
patch now and enable the builders, so all it's left for you is to start
them on your side.

Thank you very much again for your contribution!

-- 
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:[~2018-09-19 19:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-19 11:23 Rainer Orth
2018-09-19 19:46 ` Sergio Durigan Junior [this message]
2018-09-20 12:35   ` Rainer Orth
2018-09-20 14:10     ` Sergio Durigan Junior
2018-09-20 14:40       ` Sergio Durigan Junior
2018-09-20 14:44         ` Rainer Orth
2018-09-20 14:50           ` Sergio Durigan Junior
2018-09-20 17:55             ` Rainer Orth
2018-09-24 14:43               ` Rainer Orth
2018-09-24 15:25                 ` Sergio Durigan Junior
2018-09-26 13:16                   ` Sergio Durigan Junior
2018-09-26 13:33                     ` Rainer Orth
2018-09-26 14:05                       ` Sergio Durigan Junior
2018-10-05  8:48                         ` Rainer Orth
2018-10-05 15:36                           ` Sergio Durigan Junior
2018-09-21  8:51       ` Rainer Orth
2018-09-21 15:31         ` 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=874lelw9r3.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    /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).