public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: gdb@sourceware.org
Cc: Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Solaris 11 buildbots
Date: Tue, 04 Sep 2018 19:43:00 -0000	[thread overview]
Message-ID: <ydda7oxvyj1.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)

Prompted by a couple of gdb build failures in the past and Tom's message

	https://sourceware.org/ml/gdb-patches/2018-09/msg00027.html

I intend to set up gdb buildbots running on Solaris 11.4.  The current
plan is to have two buildslaves, one running on Solaris 11.4/SPARC, the
other on Solaris 11.4/x86.  I'll certainly run them to build
sparcv9-sun-solaris2.11 and amd64-pc-solaris2.11 configurations testing
64-bit debugging; if it works out reasonably well, I mean to add 32-bit
testing as well.  I don't currently plan to test i386-pc-solaris2.11 or
sparc-sun-solaris2.11 (i.e. a 32-bit gdb) or Solaris 10: the latter is
close to it's end of life and I expect to remove gcc support for that
target in about a year or two.  Besides, I don't have hosts sufficiently
secured to run buildbots there.

As mentioned in the thread above, the target isn't in the best of shapes
right now, with close to 2000 failures and 200+ racy tests, mostly in
gdb.threads.  The latter may have to be filtered out to avoid large
amounts of useless noise.  However, the buildbot will at least be able
to detect build failures early on.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

             reply	other threads:[~2018-09-04 19:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-04 19:43 Rainer Orth [this message]
2018-09-04 19:55 ` Dennis Clarke
2018-09-04 20:33   ` Rainer Orth
2018-09-04 21:28     ` Dennis Clarke
2018-09-04 21:42       ` Rainer Orth
2018-09-04 22:07         ` Dennis Clarke
2018-09-05  8:03           ` Rainer Orth

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=ydda7oxvyj1.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=gdb@sourceware.org \
    --cc=sergiodj@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).