From: Mark H Weaver <mhw@netris.org>
To: 18935@debbugs.gnu.org
Subject: bug#18935: gexp->derivation test failure
Date: Tue, 04 Nov 2014 16:44:51 -0500 [thread overview]
Message-ID: <87y4rqabe4.fsf@netris.org> (raw)
In-Reply-To: <8761euafbb.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 04 Nov 2014 21:20:08 +0100")
ludo@gnu.org (Ludovic Courtès) writes:
> Mark H Weaver <mhw@netris.org> skribis:
>
[...]
>> actual-error: (srfi-34 #<condition &nix-protocol-error [message:
>> "path
>> `/tmp/nix-build-guix-0.7.14e84b2.drv-0/source/test-tmp/store/ry17r3hm48ckcchz9ls6yhd00alyiipx-foo'
>> is not valid" status: 1] a587d68>)
>
> This can only happen if FILE in that test were deleted after its
> creation and before the ‘gexp-derivation’... which cannot even happen
> since FILE remains live for the duration of the ‘%store’ session...
> except if another daemon instance deletes it!
>
> Commit 834ea02 fixes that: it turns out that tests/nar.scm was creating
> the exact same store item, and then calling the GC to delete it.
>
> I’ll update the Guix snapshot in Guix.
Thanks!
> (In the meantime, chances are
> that you can just restart the build and won’t stumble upon this bug,
> which was unlikely to occur.)
The same failure happened to me in two consecutive build attempts:
once when running "guix system build", and then again when running
"guix build -K guix" so that I could get the failed test logs.
Mark
next prev parent reply other threads:[~2014-11-04 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 15:51 bug#18935: gexp->derivation test failure Mark H Weaver
2014-11-04 20:20 ` Ludovic Courtès
2014-11-04 21:44 ` Mark H Weaver [this message]
2014-11-05 13:33 ` Ludovic Courtès
2014-11-05 16:28 ` Mark H Weaver
2014-11-05 20:03 ` 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=87y4rqabe4.fsf@netris.org \
--to=mhw@netris.org \
--cc=18935@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.