From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 33106@debbugs.gnu.org
Subject: bug#33106: "make check-system TESTS=basic" fails on master
Date: Wed, 24 Oct 2018 14:14:04 +0200 [thread overview]
Message-ID: <87k1m75ypf.fsf@gnu.org> (raw)
In-Reply-To: <871s8gp10g.fsf@gmail.com> (Chris Marusich's message of "Tue, 23 Oct 2018 18:49:19 -0700")
Chris Marusich <cmmarusich@gmail.com> skribis:
> Chris Marusich <cmmarusich@gmail.com> writes:
>
>> I just did a Git pull; the master branch head currently points to
>> a89f731b1506b3b560f4a179da2889408dfa881d. I'm rebuilding Guix from a
>> fresh checkout of this commit. Once it's done, I'll let you know
>> whether the system test passes.
>
> It still fails, with similar error messages. For what it's worth, here
> is the output of my "uname -a":
>
> Linux garuda.local 4.18.13-gnu #1 SMP 1 x86_64 GNU/Linux
>
> I'm not sure how to proceed. For now, I'll try this: do a "guix pull"
> from a89f731b1506b3b560f4a179da2889408dfa881d, reconfigure my GuixSD
> system, and try again. I'll let you know how it goes.
Hmm, super weird. Does the machine support KVM properly? Any hints in
‘dmesg’ or /var/log/messages? Is this GuixSD running on the bare metal?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-10-24 12:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 19:09 bug#33106: "make check-system TESTS=basic" fails on master Chris Marusich
2018-10-22 13:11 ` Ludovic Courtès
2018-10-23 8:58 ` Chris Marusich
2018-10-24 1:49 ` Chris Marusich
2018-10-24 12:14 ` Ludovic Courtès [this message]
2018-10-26 5:11 ` Chris Marusich
2018-10-26 9:44 ` Ludovic Courtès
2018-10-26 16:14 ` Chris Marusich
2018-10-27 14:37 ` Ludovic Courtès
2020-11-30 21:36 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-12-19 9:08 ` zimoun
2020-12-22 14:13 ` zimoun
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=87k1m75ypf.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=33106@debbugs.gnu.org \
--cc=cmmarusich@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 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).