From: Rutger Helling <rhelling@mykolab.com>
To: ludo@gnu.org
Subject: bug#29363: Single test failure building Guix
Date: Mon, 20 Nov 2017 18:49:08 +0100 [thread overview]
Message-ID: <3050db67ea7f97da2733f9aacfef687f@mykolab.com> (raw)
In-Reply-To: <874lpp3pxw.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1084 bytes --]
Hi Ludo,
it is indeed reproducible. No matter how many times it always keeps
failing on this one test.
I've had this problem for a long time, which is a little bit annoying
since it means I have to wait until a substitute is available every
time.
On 2017-11-20 16:55, ludo@gnu.org wrote:
> 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'.
[-- Attachment #2: Type: text/html, Size: 2265 bytes --]
next prev parent reply other threads:[~2017-11-20 21:13 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
2017-11-20 17:49 ` Rutger Helling [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3050db67ea7f97da2733f9aacfef687f@mykolab.com \
--to=rhelling@mykolab.com \
--cc=ludo@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.