all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Alex Vong <alexvong1995@gmail.com>
Cc: 25256@debbugs.gnu.org
Subject: bug#25256: A lot of tests failed when building guix 0.12.0 from source
Date: Sat, 24 Dec 2016 16:36:14 -0500	[thread overview]
Message-ID: <20161224213614.GA9504@jasmine> (raw)
In-Reply-To: <CADrxHD-ooTEcM75JwftsfrDPWXDEyt9as4wnL8hrS3+EW5XqVw@mail.gmail.com>

On Sat, Dec 24, 2016 at 06:56:24AM +0000, Alex Vong wrote:
> Hello Guix,

Hi!

> Congratulation on guixsd moving to beta, maybe I should try it during
> the holiday!
> 
> A tarball with all the test logs archived is in the attachment. As
> usual, the tests are run on Debian Testing with 'uname -a' outputting
> 'Linux debian 4.8.0-2-amd64 #1 SMP Debian 4.8.11-1 (2016-12-02) x86_64
> GNU/Linux'

Thanks for the report!

I think something is fishy with the test set-up, although I'm not sure
what.

For example, this is the contents of guix-daemon.log:

1 + set -e
2 + guix-daemon --version
3 guix-daemon: unrecognized option '--version'
4 Try `guix-daemon --help' or `guix-daemon --usage' for more information.
5 FAIL tests/guix-daemon.sh (exit status: 64)

My guix-daemon does accept the '--version' option.

Can you say how you built Guix and give some more information about the
environment the tests ran in? For example, did you use `guix
environment`?

For the record, I also tried it on Debian testing with a 4.8.x kernel on
x86_64, and my only test failure is tests/syscalls.scm, which I'm going
to look into :)

  reply	other threads:[~2016-12-24 21:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-24  6:56 bug#25256: A lot of tests failed when building guix 0.12.0 from source Alex Vong
2016-12-24 21:36 ` Leo Famulari [this message]
2018-12-30  0:56 ` Alex Vong

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=20161224213614.GA9504@jasmine \
    --to=leo@famulari.name \
    --cc=25256@debbugs.gnu.org \
    --cc=alexvong1995@gmail.com \
    /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.