From: "Ludovic Courtès" <ludo@gnu.org>
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: Thu, 20 Oct 2022 11:59:34 +0200 [thread overview]
Message-ID: <871qr2hl2x.fsf@gnu.org> (raw)
In-Reply-To: <87k0514k3g.fsf@alternativebit.fr> ("Félix Baylac Jacqué"'s message of "Sat, 15 Oct 2022 09:33:23 +0200")
Hi Félix,
Félix Baylac Jacqué <felix@alternativebit.fr> skribis:
> 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.
I believe Efraim, Maxim, and probably a few other people have first-hand
experience building the whole chain. Any estimate, people?
> Is there a way to extract this information from Cuirass or the Guix data
> service?
Maybe not from the Guix Data Service, but most likely from Cuirass and
the Guix Build Coordinator.
For example, <https://ci.guix.gnu.org/build/1505621/details> shows the
duration, which could can also get with:
wget -qO- https://ci.guix.gnu.org/build/1505621 |jq
(The (guix ci) module needs an update to let you do access that info
right from Scheme.)
Now the /search interface doesn’t have a JSON equivalent, but you can
find the build ID using something along these lines:
--8<---------------cut here---------------start------------->8---
scheme@(guile-user)> ,use(guix ci)
scheme@(guile-user)> (latest-evaluations "https://ci.guix.gnu.org" 10 #:spec "master")
$14 = (#<<evaluation> id: 739193 spec: "master" complete?: #t checkouts: (#<<checkout> commit: "4716cea6256523a8ecf90a426d675bfb7620f3e4" channel: "guix">)> #<<evaluation> id: 738364 spec: "master" complete?: #t checkouts: (#<<checkout> commit: "16d4ded6302c0650978203d0df83614896c453e8" channel: "guix">)> #<<evaluation> id: 737995 spec: "master" complete?: #t checkouts: (#<<checkout> commit: "e61660c78f1190c578dd6f202bc5529cbdcff84e" channel: "guix">)> #<<evaluation> id: 737588 spec: "master" complete?: #t checkouts: (#<<checkout> commit: "88746cd80bc56212ae7922c0fa1cd9a18e44c3bb" channel: "guix">)> #<<evaluation> id: 737529 spec: "master" complete?: #t checkouts: (#<<checkout> commit: "ac553ba68e535810085dd838e48e4fa6ac553e67" channel: "guix">)> #<<evaluation> id: 736841 spec: "master" complete?: #t checkouts: (#<<checkout> commit: "7ecd85eacbfa5b7379f563b83807d3e5258cf700" channel: "guix">)> #<<evaluation> id: 734789 spec: "master" complete?: #t checkouts: (#<<checkout> commit: "3bb145b6e2a8c84e7739ead9ae76dc4d42bb9850" channel: "guix">)> #<<evaluation> id: 734747 spec: "master" complete?: #t checkouts: (#<<checkout> commit: "033cbd11a837dbc7602799f15d691221653e1996" channel: "guix">)> #<<evaluation> id: 734733 spec: "master" complete?: #t checkouts: (#<<checkout> commit: "c9eac0c3553703385c997a70741348ae5d34dc68" channel: "guix">)> #<<evaluation> id: 734718 spec: "master" complete?: #t checkouts: (#<<checkout> commit: "2589997fab07bcebe6d87fd227852389ab5b1962" channel: "guix">)>)
scheme@(guile-user)> (define jobs (evaluation-jobs "https://ci.guix.gnu.org" (evaluation-id (car $14))))
scheme@(guile-user)> (length jobs)
$15 = 76649
scheme@(guile-user)> (car jobs)
$16 = #<<job> build-id: 1627000 status: scheduled name: "0ad.aarch64-linux">
scheme@(guile-user)> ,use(srfi srfi-1)
scheme@(guile-user)> (find (lambda (job) (string=? "rust.x86_64-linux" (job-name job))) jobs)
$17 = #<<job> build-id: 1275492 status: succeeded name: "rust.x86_64-linux">
scheme@(guile-user)> (job-build "https://ci.guix.gnu.org" $17)
$18 = #<<build> id: 1275492 derivation: "/gnu/store/dmzhvql66a1n31j2xpygfxpw576wpkwb-rust-1.60.0.drv" evaluation: 579940 system: "x86_64-linux" status: succeeded timestamp: 1662284654 start-time: #<date nanosecond: 0 second: 14 minute: 44 hour: 11 day: 4 month: 9 year: 2022 zone-offset: 7200> stop-time: #<date nanosecond: 0 second: 14 minute: 44 hour: 11 day: 4 month: 9 year: 2022 zone-offset: 7200> products: ()>
--8<---------------cut here---------------end--------------->8---
That still doesn’t answer your question, because you’re interested in
the build time of the full Rust bootstrap chain, but that’s a start!
HTH,
Ludo’.
next prev parent reply other threads:[~2022-10-20 10:29 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
2022-10-20 9:59 ` Ludovic Courtès [this message]
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=871qr2hl2x.fsf@gnu.org \
--to=ludo@gnu.org \
--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).