[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#21354: closed ("make check" failure in 0.8.3)

From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#21354: closed ("make check" failure in 0.8.3)
Date: Fri, 11 Sep 2015 17:23:02 +0000

Your message dated Fri, 11 Sep 2015 19:22:07 +0200
with message-id <address@hidden>
and subject line Re: bug#21354: "make check" failure in 0.8.3
has caused the debbugs.gnu.org bug report #21354,
regarding "make check" failure in 0.8.3
to be marked as done.

(If you believe you have received this mail in error, please contact

21354: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21354
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: "make check" failure in 0.8.3 Date: Wed, 26 Aug 2015 19:54:00 +0000
I created a Vagrant virtual machine using their "ubuntu/trusty64" box (https://atlas.hashicorp.com/ubuntu/boxes/trusty64).

I connected to it via "vagrant ssh"; that gave me a shell prompt.  I can't remember whether that gave me a root prompt or not; if it didn't, then I'd have typed "sudo -s".

I ran "aptitude" and installed some packages in order to build guix from source: g++ guile-2.0-dev libbz2-dev libgcrypt11-dev libsqlite3-dev sqlite3

I unpacked the 0.8.3 source tarball into /usr/local/src.

I typed "./configure", then "make", then "make check".

I saw 


Testsuite summary for GNU Guix 0.8.3


# TOTAL: 44

# PASS: 41

# SKIP: 0

# XFAIL: 0

# FAIL: 3

# XPASS: 0

# ERROR: 0


See ./test-suite.log

Please report to address@hidden

So ... here I am, reporting it!

Attachment: test-suite.log
Description: Binary data

--- End Message ---
--- Begin Message --- Subject: Re: bug#21354: "make check" failure in 0.8.3 Date: Fri, 11 Sep 2015 19:22:07 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
address@hidden (Ludovic Courtès) skribis:

> Could you apply the given patches (you can take them from
> <http://git.savannah.gnu.org/cgit/guix.git/log/>, and then apply them
> with ‘patch -p1 < patch’ from the top-level source directory), and then
> run:
>   rm -rf test-tmp && make check
> and report the result?

I’m closing this bug.  Please reopen it if you think commits ef80ca9 and
54e515e did not fix it.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]