public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Mark Wielaard <mark@klomp.org>
Cc: Simon Marchi <simark@simark.ca>,
	 gdb-patches@sourceware.org,
	 Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [COMMITTED PATCH] Fix procfs.c compilation
Date: Wed, 13 Dec 2023 10:15:45 +0100	[thread overview]
Message-ID: <yddbkaupiny.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <20231212094050.GD14917@gnu.wildebeest.org> (Mark Wielaard's message of "Tue, 12 Dec 2023 10:40:50 +0100")

Hi Mark,

>> > We do have workers for different architectures, but they are all
>> > GNU/Linux. If you have a Solaris worker that can be used then please
>> > contact https://sourceware.org/mailman/listinfo/buildbot
>> 
>> I do: both systems (Solaris 11.4/SPARC and Solaris 11.4/amd64) used to
>> run compile-only buildbots with the previous buildmaster.
>> 
>> They are currently used for LLVM (sparcv9, amd64) and Golang (amd64)
>> buildbots, but have some free capacity.
>
> Lets discuss on the buildbot mailinglist how we can hook those up if
> you want to.

certainly.  Being pretty busy right now, I'll most like have to postpone
this to early next year.

>> >> > If you can identify a few simple and stable tests, it's possible to run
>> >> > just those (I think that's what the buildbot does even for Linux/x86
>> >> > today).  It would at least help ensure that GDB is not completely
>> >> > broken.
>> >> 
>> >> Seems like a good compromise between a pure build-only config and one
>> >> that runs the full testsuite, but drowns us in noise from timeouts and
>> >> flakiness.   I'll have a look.
>> >
>> > Currently the list of tests run for gdb is fairly small, but they are
>> > all must succeed tests (they are run under native, gdbserver and
>> > extended-gdbserver):
>> > https://sourceware.org/cgit/builder/tree/builder/master.cfg#n2883
>> 
>> I'll check if those work reliably.  In the worst case, the Solaris bots
>> would have to become compile-only, so at least guarding against build
>> failures.  However, I'm uncertain about gdbserver: I don't even know if
>> it compiles on Solaris, let alone does anything useful.
>
> We can be very flexible in what we build/test. It doesn't need to be
> the same set of tests, we can remove gdbserver build/tests for
> Solaris, etc. We can do builds on every commit, collapse builds for
> the last set of commit or just once a day.

Excellent: so we can easily tune the worker to the machine's capacity.

I've meanwhile checked that set of gdb tests: most of them seem to PASS
reliably on Solaris, while a few FAIL while they should really be
UNSUPPORTED.  As I suspected, gdbserver never has been ported to
Solaris, so that set of tests will have to be omitted.

Thanks.
	Rainer

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

  reply	other threads:[~2023-12-13  9:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30  9:54 Rainer Orth
2023-11-30 16:29 ` Simon Marchi
2023-12-01 10:09   ` Rainer Orth
2023-12-10 23:07     ` Mark Wielaard
2023-12-11 14:40       ` Rainer Orth
2023-12-12  9:40         ` Mark Wielaard
2023-12-13  9:15           ` Rainer Orth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-03-31  8:40 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=yddbkaupiny.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=gdb-patches@sourceware.org \
    --cc=mark@klomp.org \
    --cc=simark@simark.ca \
    --cc=simon.marchi@efficios.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).