From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15396] Document build dependencies
Date: Wed, 15 Mar 2023 20:56:04 +0000 [thread overview]
Message-ID: <bug-15396-163-PvGhmdsDpS@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15396-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15396
--- Comment #3 from Jan-Benedict Glaw <jbglaw@lug-owl.de> ---
Hi Thomas!
As I read through your comment again, you're running your CI builds on the
Gitlab.com platform? Or on a self-hosted system?
If it's self-hosted, you can easily change configuration to allow for longer
running jobs. All CI testing I do is strictly non-parallel (to allow to diff
log files), so it takes its time (eg. right now, a build for
qemu_aarch64_sbsa_defconfig is already running for 7h 50m right now), though
I'm not using Gitlab, but Laminar (self-hosted in my basement.) On my hardware,
I guess (don't have numbers yet) an average buildroot build will take 4.5h,
times 280 builds, resulting in some 75k build minutes just for one complete
run. That's already quite more than Gitlab.com's "Ultimate" plan. :/
While I currently pay for electricity myself, let me know if I'd do helpful
work in that area in the long run. As I do Buildroot builds only as a side
project (my main target for http://toolchain.lug-owl.de/ is to keep GCC running
for VAX, keep NetBSD for VAX alive), even running a small RasPi cluster as
build nodes would probably beneficial. It wouldn't be _fast_ either, but it
could properly build all configurations and start from the beginning once a
complete round is finished.
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-03-15 20:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 20:08 [Buildroot] [Bug 15396] New: Document build dependencies bugzilla
2023-03-14 21:29 ` [Buildroot] [Bug 15396] " bugzilla
2023-03-14 21:37 ` bugzilla
2023-03-15 20:56 ` bugzilla [this message]
2023-03-16 10:49 ` bugzilla
2023-04-03 13:25 ` bugzilla
2023-04-04 16:37 ` bugzilla
2024-06-15 15:06 ` bugzilla
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=bug-15396-163-PvGhmdsDpS@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.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