From: Tom Tromey <tom@tromey.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 0/4] Some cleanup removal
Date: Tue, 04 Sep 2018 16:58:00 -0000 [thread overview]
Message-ID: <87y3chxks6.fsf@tromey.com> (raw)
In-Reply-To: <yddo9ddy55v.fsf@CeBiTec.Uni-Bielefeld.DE> (Rainer Orth's message of "Tue, 04 Sep 2018 11:37:32 +0200")
>>>>> "Rainer" == Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
Rainer> I thought about providing Solaris 11/SPARC and x86 builders, especially
Rainer> since I now have appropriate machines running Solaris 11.4. However,
Rainer> I'm uncertain how useful that would be given that there are currently
Rainer> almost 2000 testsuite failures on x86 and 200+ racy tests. It would
Rainer> catch build failures though.
Just catching build failures would be nice. Maybe we could configure
this builder to just not run the tests, or maybe only gdb.gdb tests.
Because the builders compare against baseline results, I think it is the
large number of racy tests that is more of a problem than the number of
failures.
Tom
next prev parent reply other threads:[~2018-09-04 16:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 19:03 Tom Tromey
2018-09-03 19:02 ` [PATCH 1/4] Remove cleanup from add_path Tom Tromey
2018-09-03 19:03 ` [PATCH 4/4] Remove cleanup from try_open_exec_file Tom Tromey
2018-09-03 19:03 ` [PATCH 2/4] Remove cleanup from procfs.c Tom Tromey
2018-09-04 10:50 ` Rainer Orth
2018-09-04 16:56 ` Tom Tromey
2018-09-03 19:03 ` [PATCH 3/4] Return std::string from gdb_bfd_errmsg Tom Tromey
2018-09-04 9:37 ` [PATCH 0/4] Some cleanup removal Rainer Orth
2018-09-04 16:58 ` Tom Tromey [this message]
2018-09-04 18:30 ` Rainer Orth
2018-09-13 22:41 ` Tom Tromey
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=87y3chxks6.fsf@tromey.com \
--to=tom@tromey.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