all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: 40650@debbugs.gnu.org
Subject: bug#40650: guix test suite failures building Debian package
Date: Sat, 18 Apr 2020 22:00:37 +0200	[thread overview]
Message-ID: <877dyc5ztm.fsf@gnu.org> (raw)
In-Reply-To: <87sgh14v6y.fsf@yucca> (Vagrant Cascadian's message of "Fri, 17 Apr 2020 15:13:41 -0700")

Vagrant Cascadian <vagrant@debian.org> skribis:

> test-name: gexp->derivation #:references-graphs
> location: /build/guix-YPdZIs/guix-1.1.0/tests/gexp.scm:944

[...]

> actual-value: #f
> result: FAIL

This failure is because of this assumption in the test:

         ;; Note: %BOOTSTRAP-GUILE depends on the bootstrap Bash.
         (lset= string=?
                (call-with-input-file g-guile read)
                (list (derivation->output-path guile-drv) bash))

This assumption does not hold if you use a ‘bash’ binary different from
the one Guix provides; I had overlooked this.

You can either solve this by pre-downloading Guix’ statically-linked
{bash,mkdir,xz,tar} as discussed earlier, or simply by skipping this
test by adding (test-skip 1) above it (it’s not unreasonable IMO).

Ludo’.

  parent reply	other threads:[~2020-04-18 20:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-15 22:03 bug#40650: guix test suite failures building Debian package Vagrant Cascadian
2020-04-16  8:40 ` Ludovic Courtès
2020-04-16 17:23   ` Vagrant Cascadian
2020-04-17  8:50     ` Ludovic Courtès
2020-04-17 22:13       ` Vagrant Cascadian
2020-04-18 19:53         ` bug#40650: ‘scandir*’ test failure Ludovic Courtès
2020-04-18 20:19           ` Vagrant Cascadian
2020-04-19 11:01             ` Ludovic Courtès
2020-04-18 20:00         ` Ludovic Courtès [this message]
2020-04-18 20:02         ` bug#40650: guix test suite failures building Debian package Ludovic Courtès

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=877dyc5ztm.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=40650@debbugs.gnu.org \
    --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 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.