From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: [Buildroot] Call for more autobuilder machines
Date: Wed, 7 Feb 2024 15:06:16 +0100 [thread overview]
Message-ID: <20240207150616.2683d894@windsurf> (raw)
Dear Buildroot community members,
Our "autobuilder" infrastructure, whose results are presented at
http://autobuild.buildroot.net/, and sent on a daily basis to the
mailing list and individual developers, is critical to the proper
testing of Buildroot.
Unfortunately, over recent times, less and less machines have been
contributing build results, to the point where we only test 100-120
builds per day, which is not enough to have good coverage.
Indeed, the builds are done by various machines that contribute their
results to autobuild.buildroot.net. Therefore, the way to increase the
number of builds done per day is to increase the number of machines
that contributes to the build.
So this e-mail is a call for participation: if you have some machines
that could be used to run Buildroot builds 24/7, or at least during the
night and/or week-end, it would be useful.
However, beware that it only makes sense to contribute if you have a
sufficiently powerful machine at hand: enough RAM, fast storage,
recently recent CPU. At least 4 cores (not threads), 32 GB of RAM, and
SSD/NVMe.
If you are interested in contributing to this, contact us and we will
give you the details. It's pretty much as simple as running
https://git.buildroot.org/buildroot-test/tree/scripts/autobuild-run on
your machine, as an unprivileged user (no root/sudo access needed), and
that's it.
Thanks a lot for your collaboration!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2024-02-07 14:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240207150616.2683d894@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.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