From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: [Buildroot] Autobuild server migrated
Date: Sun, 18 Aug 2024 14:44:28 +0200 [thread overview]
Message-ID: <20240818144428.7e5078d6@windsurf> (raw)
Hello,
We have migrated autobuild.buildroot.org to a new server. The DNS
entries have just been updated by Peter, so it might take a little
while for you to have the new DNS entry. The new server IP address is
138.201.205.61, the old server IP address is 94.23.254.152.
The old server was a super old dual core Intel(R) Atom(TM) CPU D425
machine, with only a spinning hard drive. It was really, really slow.
Also, it was owned/rented by me personally.
The new server is a 4 cores (x2 threads) Intel(R) Xeon(R) CPU E3-1275
v5 @ 3.60GHz machine, with NVMe storage, that the Buildroot Association
is renting (please become a member of the association to support it, or
ask your company to sponsor).
The new server is therefore much more responsive, especially when
searching through build results. A few hints for those of you who may
not be familiar:
- You can create some search queries by manipulating the URL. For
example:
http://autobuild.buildroot.org/?reason=host-gcc-final%
will list all build failures related to *any* version of
host-gcc-final (% acts as a wildcard)
http://autobuild.buildroot.net/?reason=host-gcc-final%&arch=powerpc64le
will list all build failures related to any version of
host-gcc-final, which occurred on powerpc64le
You can also combine that with
&libc=musl&subarch=power8&branch=master for example
- http://autobuild.buildroot.net/search.php provides much more advanced
search capabilities. Most notably, you can search build results based
on config options. You can for example search all build results that
have BR2_PACKAGE_SYSTEMD=y, or any other option.
This is particularly useful if you are looking at a package build
failure, and wondering if this package was ever built as part of a
fully successful build.
This search used to be painfully slow on the old server. It is now
still a bit slow, but much more usable.
Back to the server: we intend to migrate the official web site
(https://www.buildroot.org) to this new server, and also our
backup mirror (https://sources.buildroot.net), in an effort
to consolidate our infrastructure.
Best regards,
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-08-18 12:44 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=20240818144428.7e5078d6@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