unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Rutger Helling <rhelling@mykolab.com>
Cc: 29363@debbugs.gnu.org
Subject: bug#29363: Single test failure building Guix
Date: Mon, 20 Nov 2017 16:55:23 +0100	[thread overview]
Message-ID: <874lpp3pxw.fsf@gnu.org> (raw)
In-Reply-To: <89edb4cc307bfae5db7812abe3b4a37a@mykolab.com> (Rutger Helling's message of "Mon, 20 Nov 2017 11:08:59 +0100")

Hi Rutger,

Rutger Helling <rhelling@mykolab.com> skribis:

> test-name: dead path can be explicitly collected
> location: /tmp/guix-build-guix-0.13.0-10.0b4c385.drv-0/source/tests/store.scm:178
> source:
> + (test-assert
> +   "dead path can be explicitly collected"
> +   (let ((p (add-text-to-store
> +              %store
> +              "random-text"
> +              (random-text)
> +              '())))
> +     (let-values
> +       (((paths freed) (delete-paths %store (list p))))
> +       (and (equal? paths (list p))
> +            (> freed 0)
> +            (not (file-exists? p))))))
> actual-value: #f
> result: FAIL

I didn’t experience this on my laptop.  Is it reproducible if you run
“guix build guix” a second time?

Thanks,
Ludo’.

  reply	other threads:[~2017-11-20 15:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 10:08 bug#29363: Single test failure building Guix Rutger Helling
2017-11-20 15:55 ` Ludovic Courtès [this message]
2017-11-20 17:49   ` Rutger Helling
2017-11-21  0:31 ` Marius Bakke
2017-11-21  7:31   ` Rutger Helling
2017-11-21  7:47   ` Ludovic Courtès
2017-11-21  9:10     ` Rutger Helling
2017-11-21 12:53       ` Ludovic Courtès
2017-11-21 14:50         ` Rutger Helling
2017-11-21 21:11           ` Marius Bakke
2017-11-21 21:39     ` Marius Bakke
2017-11-22 15:55       ` 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

  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=874lpp3pxw.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=29363@debbugs.gnu.org \
    --cc=rhelling@mykolab.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).