From: "Ludovic Courtès" <ludo@gnu.org>
To: Marius Bakke <marius@gnu.org>
Cc: Mathieu Othacehe <othacehe@gnu.org>, 58203@debbugs.gnu.org
Subject: bug#58203: Cuirass fails to respect (target-x86-32?) in some circumstances
Date: Wed, 05 Oct 2022 14:51:06 +0200 [thread overview]
Message-ID: <87wn9eqvr9.fsf@gnu.org> (raw)
In-Reply-To: <8735c7yjk4.fsf@gnu.org> (Marius Bakke's message of "Sat, 01 Oct 2022 11:33:47 +0200")
Hi Marius,
(Cc: Mathieu for the search box issue below.)
Marius Bakke <marius@gnu.org> skribis:
> Ludovic Courtès <ludo@gnu.org> skriver:
[...]
>> The good news is that with today’s ‘staging’, everything’s fine:
>
> Not quite:
>
> https://ci.guix.gnu.org/search?query=system%3Ai686-linux+imath
>
> Imath has no dependencies apart from CMake, so all of those should be
> the same derivation, yet some are failing.
This is for:
/gnu/store/sdgcjk8wiv4wk69nlxwp43adppmvijpz-imath-3.1.3.drv
which has #:tests? #true… but that’s also from an evaluation from May,
even if the build is from Sep. 30:
https://ci.guix.gnu.org/build/739643/details
https://ci.guix.gnu.org/eval/302107
From <https://ci.guix.gnu.org/eval/683442/dashboard?system=i686-linux>,
I found this recent build ✅:
https://ci.guix.gnu.org/build/1324091/details
It’s a bug that we don’t get it from the search box:
https://ci.guix.gnu.org/search?query=spec%3Astaging+system%3Ai686-linux+imath
Mathieu, any ideas?
Anyhow, the “ground truth” in general is Guix itself:
guix time-machine --branch=staging -- \
build imath -s i686-linux --no-grafts
Thanks,
Ludo’.
prev parent reply other threads:[~2022-10-05 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 21:12 bug#58203: Cuirass fails to respect (target-x86-32?) in some circumstances Marius Bakke
2022-09-30 22:14 ` Ludovic Courtès
2022-10-01 9:33 ` Marius Bakke
2022-10-05 12:51 ` Ludovic Courtès [this message]
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=87wn9eqvr9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=58203@debbugs.gnu.org \
--cc=marius@gnu.org \
--cc=othacehe@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 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.