From: Pierre Langlois <pierre.langlois@gmx.com>
To: Leo Famulari <leo@famulari.name>
Cc: vagrant@debian.org, aikokyle@gmail.com, 52943@debbugs.gnu.org
Subject: bug#52943: Cannot build guix as part of guix system reconfigure after commit 224d437fb4 on aarch64
Date: Sat, 29 Jan 2022 21:35:27 +0000 [thread overview]
Message-ID: <87zgne9q2g.fsf@gmx.com> (raw)
In-Reply-To: <YfWsUoWtOhMDlLm9@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 1412 bytes --]
Leo Famulari <leo@famulari.name> writes:
> On Sat, Jan 29, 2022 at 08:54:24PM +0000, Pierre Langlois wrote:
>> > Since the 'guix' package still does not build on aarch64, I'm reopening
>> > this bug.
>>
>> Oh it doesn't? What hash are you on?
>
> I'm not using aarch64, so I can't give a commit hash. I am observing the
> build farm's support for aarch64.
>
>> I'm currently on b14a1cdef571c0901f716f4e752a97e8028ccbbd on a RockPro64
>> and it's working OK, maybe something changed since then although this
>> hash isn't very old. I see the farm does not have any substitutes yet.
>
> As you point out, the build farm cannot build it:
>
> https://ci.guix.gnu.org/search?query=spec%3Amaster+system%3Aaarch64-linux+guix-1.3.0
>
> Maybe it's a problem with in the 'guix' package, maybe in the some other
> package. But the effect for users is the same, and they report things
> like this:
>
> https://issues.guix.gnu.org/53616
Oh I see, I'm not familiar with how the infra works, but it looks like
aarch64 jobs aren't currently scheduled at all: https://ci.guix.gnu.org/build/337714/details
Maybe we could restart it and see if we can reproduce the problem? I
wonder if there's a good reason for jobs not being scheduled, I saw
recent commits regarding new aarch64 HW being set up.
I'll be happy to help debug build issues when we know more of course!
Thanks,
Pierre
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 519 bytes --]
next prev parent reply other threads:[~2022-01-29 21:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-01 23:54 bug#52943: Cannot build guix as part of guix system reconfigure after commit 224d437fb4 on aarch64 Aiko Kyle
2022-01-02 2:13 ` Leo Famulari
2022-01-02 4:11 ` Aiko Kyle
2022-01-02 4:51 ` Leo Famulari
2022-01-02 6:36 ` Aiko Kyle
2022-01-03 21:38 ` Akira Kyle
2022-01-04 1:13 ` Akira Kyle
2022-01-04 1:16 ` Akira Kyle
2022-01-09 4:39 ` Chris Marusich
2022-01-15 13:27 ` Pierre Langlois
2022-01-16 1:00 ` Chris Marusich
2022-01-17 4:46 ` Chris Marusich
2022-01-17 18:51 ` Pierre Langlois
2022-01-18 5:33 ` Vagrant Cascadian
2022-01-19 19:28 ` Vagrant Cascadian
2022-01-29 18:33 ` Leo Famulari
2022-01-29 20:54 ` Pierre Langlois
2022-01-29 21:06 ` Leo Famulari
2022-01-29 21:35 ` Pierre Langlois [this message]
2022-10-07 8:48 ` Christopher Baines
2022-10-20 14:57 ` Mathieu Othacehe
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=87zgne9q2g.fsf@gmx.com \
--to=pierre.langlois@gmx.com \
--cc=52943@debbugs.gnu.org \
--cc=aikokyle@gmail.com \
--cc=leo@famulari.name \
--cc=vagrant@debian.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).