From: Luis Machado <luis.machado@linaro.org>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: [RFC] Proposal for hosting GDB CI builds
Date: Tue, 20 Jul 2021 12:21:17 -0300 [thread overview]
Message-ID: <519a40f4-5999-f338-227e-464ed7ce23be@linaro.org> (raw)
In-Reply-To: <7bfae273-3887-30c8-dc65-94d5b177db56@linaro.org>
Any other feedback on this?
On 6/30/21 1:46 PM, Luis Machado wrote:
> Hi,
>
> This proposal comes as an attempt to revive the GDB CI builds, given the
> previous one (buildbot) is no longer being maintained by Sergio (thanks
> a lot for keeping it working for all these years by the way).
>
> CI GDB builds are a great help for spotting regressions without having
> to do the tedious and time-consuming work of running the GDB testsuite
> for each git revision, for each architecture and reading through
> hundreds of lines of summaries. If a regression is spotted, then one
> needs to bisect to find the culprit. This isn't great, specially for
> architectures without great availability of desktop hardware.
>
> Ideally, for each commit, we'd run full builds to validate the state of
> the tree, but we're not quite there yet. So meanwhile, having some level
> of automation to get the builds done without manual intervention sounds
> like a reasonable step forward.
>
> From previous IRC conversations, it seems to be a consensus that
> availability of processing power is not a problem. It is reasonably easy
> to find hardware to do some builds. The most difficult resource to find
> is manpower to setup the CI infrastructure and keep it running.
>
> With the above said, I've discussed this internally at Linaro and we can
> spare some manpower to setup and maintain an isolated Linaro-hosted
> Jenkins instance for GDB CI builds.
>
> Linaro can take care of providing builders and build jobs for ARM. Other
> architectures would be handled by their respective contributors. Those
> contributors can write jobs and plug builders as needed.
>
> Setting up new jobs doesn't require the use of the web interface. It can
> be done with yaml files in a git repo. It is reasonably simple.
>
> You can see an example of the Linaro CI here: https://ci.linaro.org/
>
> Also, a GDB job for aarch64: https://ci.linaro.org/job/tcwg-gdb/
>
> And also the summaries for GDB testsuite runs:
> https://ci.linaro.org/job/tcwg-compare-results/13968/artifact/artifacts/logs/0-report.html
>
>
> Of course, this effort only makes sense if the community is OK with
> using Jenkins as the CI mechanism and if it actually sees value in
> having a system like this in place.
>
> Thoughts? Questions?
next prev parent reply other threads:[~2021-07-20 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 16:46 Luis Machado
2021-07-01 9:40 ` Rainer Orth
2021-07-01 11:48 ` Luis Machado
2021-07-01 12:06 ` Rainer Orth
2021-07-01 13:10 ` Luis Machado
2021-07-02 9:05 ` Rainer Orth
2021-07-01 11:37 ` Christophe LYON
2021-07-01 11:50 ` Luis Machado
2021-07-01 12:08 ` Rainer Orth
2021-07-20 15:21 ` Luis Machado [this message]
2021-07-23 20:17 ` Simon Marchi
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=519a40f4-5999-f338-227e-464ed7ce23be@linaro.org \
--to=luis.machado@linaro.org \
--cc=gdb@sourceware.org \
/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).