unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Ian Eure <ian@retrospec.tv>
To: 75205@debbugs.gnu.org
Cc: "Ludovic Courtès" <ludo@gnu.org>
Subject: bug#75205: guix package test failure on i686-linux (kexec-load-file test)
Date: Tue, 31 Dec 2024 20:17:09 -0800	[thread overview]
Message-ID: <87seq3uq0q.fsf@retrospec.tv> (raw)
In-Reply-To: <781419f2-6304-4c18-b01c-412121126ee5@posteo.net>

This is failing for me on aarch64-linux also:

    test-name: kexec-load-file
    location: 
    /tmp/guix-build-guix-1.4.0-31.121e96d.drv-0/source/tests/syscalls.scm:688
    source:
    + (test-equal
    +   "kexec-load-file"
    +   EPERM
    +   (catch 'system-error
    +          (lambda ()
    +            (let ((fd1 (open-fdes "/dev/null" O_RDONLY))
    +                  (fd2 (open-fdes "/dev/null" O_RDONLY)))
    +              (kexec-load-file fd1 fd2 "gnu.repl=yes")))
    +          (lambda args (system-error-errno args))))
    expected-value: 1
    actual-value: 38
    result: FAIL

If I downgrade to commit 96cd163c14e68c66c6a4cf0b18261fc454f8c1ba, 
guix tests pass again -- the failing test was added in the next 
commit.  I’m not sure what the issue here, it seems like that 
syscall shouldn’t be arch-dependent, and the errnos in the 
failures are unhelpful.  38 is ERANGE, 14 is EFAULT, neither of 
those seem applicable here.  EPERM is 1, and 38 doesn’t have its 
LSB set, so it can’t be a bitmask.

I’m encountering the issue using Guix as a foreign package manager 
on top of Debian 12 "bookworm" in a VM.  Perhaps there’s an 
implicit dependency on the host system’s kernel in the test, which 
Debian’s fails to meet.

Ludo’, any thoughts?

  -- Ian




  reply	other threads:[~2025-01-01  4:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-30 16:55 bug#75205: guix package test failure on i686-linux (kexec-load-file test) Dariqq
2025-01-01  4:17 ` Ian Eure [this message]
2025-01-04 18:11   ` 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

  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=87seq3uq0q.fsf@retrospec.tv \
    --to=ian@retrospec.tv \
    --cc=75205@debbugs.gnu.org \
    --cc=ludo@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).