From: Luis Machado <luis.machado@linaro.org>
To: Sergio Durigan Junior <sergiodj@sergiodj.net>,
Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gdb@sourceware.org
Subject: Re: Request for help with the Buildbot [was: Re: Status of GDB buildbots]
Date: Thu, 27 Aug 2020 16:31:38 -0300 [thread overview]
Message-ID: <83ebccde-b99b-408b-2bb3-23ab3a7613cc@linaro.org> (raw)
In-Reply-To: <87y2m2rdcz.fsf_-_@paluero>
Hi,
On 8/25/20 11:47 AM, Sergio Durigan Junior via Gdb wrote:
> On Tuesday, August 25 2020, Rainer Orth wrote:
>
>> Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE> writes:
>>
>>> It seems regular scheduled runs of the GDB buildbots stopped about a
>>> month ago. AFAICS all runs since (which are only a few) are for the
>>> racy and try_ssh schedulers only, nothing for master.
>>>
>>> I've initially observed this on the Solaris buildbots, but the others
>>> seem to be equally affected. For the Solaris bots, there are regular
>>> keepalive messages in twistd.log, but nothing else.
>>
>> I've never received a reply on this one and now found that Sergio has
>> left RedHat. Given that the buildbots have been mostly idle for a month
>> or two: is there anyone to look into this?
>
> Hi Rainer,
>
> Sorry about the disappearance; indeed I'm not at RH anymore, and
> although I'm trying to follow gdb-patches, I'm not subscribed to gdb@
> anymore, which means I completely missed your message :-/.
Is this something RH will pick up or is it a best-effort personal
contribution of yours?
>
> Anyway, I was not aware of this problem with our buildbot. I thought
> I'd be able to maintain it while doing my other job, but as it turns out
> it's just too much. So I'm hijacking this thread and turning it into a
> request for help with our Buildbot.
>
> I don't know how much value the Buildbot still brings to the community.
> I know a few people were relying heavily on it because of the try build
> feature, but I'm not sure if they still use it. That's something for
> the community to discuss, I think.
I can state it brings pretty good value to arm-linux/aarch64-linux
testing. I've been noticing an influx of regressions from pushed patches
that have not been properly exercised on aarch64-linux, which is
unfortunate.
Ideally we'd have a CI loop integrated with some patch reviewing system
(gerrit was great in this regard), but the buildbot is already a great
improvement over not having anything.
next prev parent reply other threads:[~2020-08-27 19:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 14:24 Status of GDB buildbots Rainer Orth
2020-08-25 10:45 ` Rainer Orth
2020-08-25 14:47 ` Request for help with the Buildbot [was: Re: Status of GDB buildbots] Sergio Durigan Junior
2020-08-27 19:31 ` Luis Machado [this message]
2020-08-27 19:36 ` 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=83ebccde-b99b-408b-2bb3-23ab3a7613cc@linaro.org \
--to=luis.machado@linaro.org \
--cc=gdb@sourceware.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
--cc=sergiodj@sergiodj.net \
/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).