From: Efraim Flashner <efraim@flashner.co.il>
To: "Félix Baylac Jacqué" <felix@alternativebit.fr>
Cc: guix-devel@gnu.org
Subject: Re: How long does it take to run the full rustc bootstrap chain?
Date: Wed, 19 Oct 2022 22:52:07 +0300 [thread overview]
Message-ID: <Y1BVZ71UBdjp0MbN@3900XT> (raw)
In-Reply-To: <87k0514k3g.fsf@alternativebit.fr>
[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]
On Sat, Oct 15, 2022 at 09:33:23AM +0200, Félix Baylac Jacqué wrote:
> Hey Guix,
>
> I'd be curious to know how long it takes to run the full rustc bootstrap
> chain on the Guix build farm. I'm sadly not sure how to approach this
> problem.
>
> Is there a way to extract this information from Cuirass or the Guix data
> service?
If I were to go about it I would try to get the build log from each
package:
guix build --no-grafts -e '(@@ (gnu packages rust) rust-bootstrap)' \
--log-file
and then I'd add up the build and test phases to get a rough estimate.
For an approximate answer, the build farm runs 4 builds per machine,
with 8 cores per build (all of this is in the guix-maintenance repo I
think). When I build from mrustc to rust-1.60 on my machine with 24
cores it currently takes about 2 hours for rust-bootstrap (1.54) and
then about 30-45 minutes each other version.
I don't remember the bug number offhand, but there's work being done to
speed up the process. The last time I ran though the test build I built
from rust-1.55 to librsvg in 171 minutes.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-10-19 20:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 7:33 How long does it take to run the full rustc bootstrap chain? Félix Baylac Jacqué
2022-10-19 19:52 ` Efraim Flashner [this message]
2022-10-20 9:59 ` Ludovic Courtès
2022-10-20 20:11 ` Efraim Flashner
2022-10-22 8:57 ` Félix Baylac Jacqué
2022-10-22 13:48 ` Maxim Cournoyer
2022-10-26 19:37 ` bokr
2022-10-27 14:35 ` Maxim Cournoyer
2022-10-28 12:00 ` Has guix system ever run a hardware survey? Joshua Branson
2022-10-31 19:02 ` How long does it take to run the full rustc bootstrap chain? Bengt Richter
2022-11-01 12:49 ` Maxim Cournoyer
2022-11-06 9:08 ` Efraim Flashner
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y1BVZ71UBdjp0MbN@3900XT \
--to=efraim@flashner.co.il \
--cc=felix@alternativebit.fr \
--cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).