From: someone@selfhosted.xyz
To: 26929@debbugs.gnu.org
Subject: bug#26929: guix build errors
Date: Sun, 14 May 2017 14:55:34 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.20.1705141453570.8823@localhost> (raw)
Hi, this is my first email to this list.
I ran into build errors twice when running guix pull from the guixSD usb install image and was asked to report it:
Testsuite summary for GNU Guix
============================================================================
# TOTAL: 704
# PASS: 670
# SKIP: 32
# XFAIL: 0
# FAIL: 2
# XPASS: 0
# ERROR: 0
============================================================================
See ./test-suite.log
Please report to bug-guix@gnu.org
============================================================================
make[4]: *** [Makefile:4348: test-suite.log] Error 1
make[4]: Leaving directory '/tmp/guix-build-guix-0.12.0-10.ba2260d.drv-0/source'
make[3]: *** [Makefile:4456: check-TESTS] Error 2
make[3]: Leaving directory '/tmp/guix-build-guix-0.12.0-10.ba2260d.drv-0/source'
make[2]: *** [Makefile:4696: check-am] Error 2
make[2]: Leaving directory '/tmp/guix-build-guix-0.12.0-10.ba2260d.drv-0/source'
make[1]: *** [Makefile:4233: check-recursive] Error 1
make[1]: Leaving directory '/tmp/guix-build-guix-0.12.0-10.ba2260d.drv-0/source'
make: *** [Makefile:4698: check] Error 2
phase `check' failed after 475.3 seconds
builder for `/gnu/store/n0xa06kksp3wmjiq31j3dcdci2jwc9sx-guix-0.12.0-10.ba2260d.drv' failed with exit code 1
guix system: error: build failed: build of `/gnu/store/n0xa06kksp3wmjiq31j3dcdci2jwc9sx-guix-0.12.0-10.ba2260d.drv' failed
next reply other threads:[~2017-05-14 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-14 12:55 someone [this message]
2017-05-14 17:05 ` bug#26929: guix build errors Leo Famulari
[not found] ` <alpine.LNX.2.20.1705141907510.8823@localhost>
2017-05-14 17:18 ` Leo Famulari
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=alpine.LNX.2.20.1705141453570.8823@localhost \
--to=someone@selfhosted.xyz \
--cc=26929@debbugs.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.