all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: myglc2 <myglc2@gmail.com>
To: 22593@debbugs.gnu.org
Subject: bug#22593: 'make check' fails
Date: Mon, 08 Feb 2016 23:11:22 -0500	[thread overview]
Message-ID: <8760xy7cb9.fsf@gmail.com> (raw)
In-Reply-To: <87mvrchy6d.fsf@gmail.com>

ludo@gnu.org (Ludovic Courtès) writes:

> myglc2 <myglc2@gmail.com> skribis:
>
>> tests/store.scm:705: FAIL verify-store
>> tests/store.scm:722: FAIL verify-store + check-contents
>
> Here we see two failures…
>
>> ============================================================================
>> Testsuite summary for GNU Guix 0.9.1
>> ============================================================================
>> # TOTAL: 59
>> # PASS:  59
>> # SKIP:  0
>> # XFAIL: 0
>> # FAIL:  0
>> # XPASS: 0
>> # ERROR: 0
>> ============================================================================
>
> … but this log shows zero failures.
>
> Could you run ‘make check’ again a see if the failures show up?  You can
> also start from a fresh state by running ‘rm -rf test-tmp’ in the build
> tree before ‘make check’.
>
> TIA,
> Ludo’.
I mis-read your email and failed to run 'make check' before ‘rm -rf
test-tmp’, so I don't have a response to your first request.  Apologies
for dropping the ball.

FWIW, I ran 'make check' twice before sending the first email. I
observed failures at the same point in each. I would send you the 2nd
earlier failure but unfortunately I discarded it. 

Finally, after ‘rm -rf test-tmp’, 'make check' completed with zero
failures.

Best, George

  reply	other threads:[~2016-02-09  4:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-07 23:56 bug#22593: 'make check' fails myglc2
2016-02-08 22:45 ` Ludovic Courtès
2016-02-09  4:11   ` myglc2 [this message]
2016-02-09 21:06     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8760xy7cb9.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=22593@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.