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: Thu, 20 Sep 2018 14:40:00 -0000 [thread overview]
Message-ID: <87fty4teps.fsf@redhat.com> (raw)
In-Reply-To: <877ejguuo0.fsf@redhat.com> (Sergio Durigan Junior's message of "Thu, 20 Sep 2018 10:10:07 -0400")
On Thursday, September 20 2018, I wrote:
> On Thursday, September 20 2018, Rainer Orth wrote:
>
>> Hi Sergio,
>>
>>> 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.
>>
>> great. It will save me the trouble of detecting post-factum when some
>> patch broke the Solaris build ;-)
>
> Yeah, that's currently the main feature being used in our BuildBot: the
> breakage emails.
Hey Rainer,
So, there were a few problems in the master.cfg file which prevented the
builders to actually build GDB. I fixed them, and they're now
processing the queue. However, the builds are failing. For example:
https://gdb-build.sergiodj.net/builders/Solaris11-sparcv9-m64/builds/3/steps/compile%20gdb/logs/stdio
This seems to be the problem you were talking about, regarding
unittests/string_view-selftests.o. You mentioned that this breakage
shouldn't happen if we don't use -D_GLIBCXX_DEBUG, right? Can you
please take a look at this?
For now, I've disabled the email notifications for the Solaris builders.
Cheers,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
next prev parent reply other threads:[~2018-09-20 14:40 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
2018-09-20 12:35 ` Rainer Orth
2018-09-20 14:10 ` Sergio Durigan Junior
2018-09-20 14:40 ` Sergio Durigan Junior [this message]
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=87fty4teps.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).