From: Mathieu Othacehe <othacehe@gnu.org>
To: 57215@debbugs.gnu.org
Cc: Tobias Geerinckx-Rice <me@tobias.gr>
Subject: bug#57215: ci: Fail to evaluate Guix specification
Date: Tue, 16 Aug 2022 09:56:02 +0200 [thread overview]
Message-ID: <87pmh0fwq5.fsf@gnu.org> (raw)
In-Reply-To: <87mtc5d64w.fsf@gnu.org> (Mathieu Othacehe's message of "Mon, 15 Aug 2022 14:48:47 +0200")
Hello,
Some news on this one: I discovered that the evaluation failure of the
"guix" specification is correlated with the selected systems. When
disabling "aarch64-linux" and "powerpc64le-linux", the evaluation
succeeded.
Now, when running:
--8<---------------cut here---------------start------------->8---
mathieu@berlin ~$ guix pull -s powerpc64le-linux -v3
Updating channel 'guix' from Git repository at 'https://git.savannah.gnu.org/git/guix.git'...
Building from this channel:
guix https://git.savannah.gnu.org/git/guix.git 0598b5d
building /gnu/store/m7ppw9lb65g99dajwkb56w05zqmydsdh-guile-bootstrap-2.0.drv...
@ unsupported-platform /gnu/store/m7ppw9lb65g99dajwkb56w05zqmydsdh-guile-bootstrap-2.0.drv powerpc64le-linux
while setting up the build environment: a `powerpc64le-linux' is required to build `/gnu/store/m7ppw9lb65g99dajwkb56w05zqmydsdh-guile-bootstrap-2.0.drv', but I am a `x86_64-linux'
builder for `/gnu/store/m7ppw9lb65g99dajwkb56w05zqmydsdh-guile-bootstrap-2.0.drv' failed with exit code 1
build of /gnu/store/m7ppw9lb65g99dajwkb56w05zqmydsdh-guile-bootstrap-2.0.drv failed
View build log at '/var/log/guix/drvs/m7/ppw9lb65g99dajwkb56w05zqmydsdh-guile-bootstrap-2.0.drv.gz'.
--8<---------------cut here---------------end--------------->8---
It fails in the same way with aarch64-linux. That's because there's no
offload or binfmt mechanism on berlin at the moment.
I restored the /etc/guix/machines.scm to enable offloading, and
suddenly "aarch64-linux" system is working again for the "guix"
specification. "powerpc64le-linux" is still failing as we do not have a
machine for that architecture currently available: p9.tobias.gr is
commented out.
Tobias, I'm not sure to remember why?
Now there are multiple unclear points to me:
1. Why do we need an available machine with the foreign architecture to
compute the corresponding "guix" derivation? Note that the evaluation of
package derivations for foreign systems works even though a
corresponding machine is not available:
--8<---------------cut here---------------start------------->8---
mathieu@berlin ~$ guix build -s powerpc64le-linux -d hello
/gnu/store/spzmh79qi21k26p15w27r3jjg95szg17-hello-2.12.1.drv
--8<---------------cut here---------------end--------------->8---
2. Why the following traces are not reported back by the inferior in
charge of the evaluation of the "guix" derivation?
--8<---------------cut here---------------start------------->8---
@ unsupported-platform /gnu/store/m7ppw9lb65g99dajwkb56w05zqmydsdh-guile-bootstrap-2.0.drv powerpc64le-linux
while setting up the build environment: a `powerpc64le-linux' is required to build `/gnu/store/m7ppw9lb65g99dajwkb56w05zqmydsdh-guile-bootstrap-2.0.drv', but I am a `x86_64-linux'
builder for `/gnu/store/m7ppw9lb65g99dajwkb56w05zqmydsdh-guile-bootstrap-2.0.drv' failed with exit code 1
build of /gnu/store/m7ppw9lb65g99dajwkb56w05zqmydsdh-guile-bootstrap-2.0.drv failed
--8<---------------cut here---------------end--------------->8---
3. Why does the "cuirass evaluate" process crashes when an inferior
crashes (see the backtrace in my previous email)?
I'll try to come-up with simple reproducers for those different points.
In the meantime, the "guix" specification is working again for
x86_64-linux, i686-linux and aarch64-linux systems which is a good news.
Thanks,
Mathieu
next prev parent reply other threads:[~2022-08-16 7:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-14 19:56 bug#57215: ci: Fail to evaluate Guix specification Mathieu Othacehe
2022-08-15 12:01 ` Mathieu Othacehe
2022-08-15 12:48 ` Mathieu Othacehe
2022-08-16 7:56 ` Mathieu Othacehe [this message]
2022-08-16 8:41 ` Christopher Baines
2022-08-16 9:20 ` Mathieu Othacehe
2022-08-16 10:56 ` Christopher Baines
2022-08-19 14:19 ` Maxim Cournoyer
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=87pmh0fwq5.fsf@gnu.org \
--to=othacehe@gnu.org \
--cc=57215@debbugs.gnu.org \
--cc=me@tobias.gr \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.