unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Roel Janssen <roel@gnu.org>
Cc: 29676@debbugs.gnu.org
Subject: bug#29676: Guix test failure on tests/store.
Date: Tue, 12 Dec 2017 21:22:25 +0100	[thread overview]
Message-ID: <871sjzitmm.fsf@gnu.org> (raw)
In-Reply-To: <87shcfdh5w.fsf@gnu.org> (Roel Janssen's message of "Tue, 12 Dec 2017 17:50:35 +0100")

Roel Janssen <roel@gnu.org> skribis:

> Ludovic Courtès writes:
>
>> Hi,
>>
>> Roel Janssen <roel@gnu.org> skribis:
>>
>>> I attached the build log.  The relevant bit is this:
>>>
>>> actual-error:
>>> + (srfi-34
>>> +   #<condition &nix-protocol-error [message: "path `dtmp/guix-tests/store/462z3fnl7bs44vp9s97jyg1z74nsfvly-tar' is not in the Nix store" status: 1] 1071090>)
>>> result: FAIL
>>
>> The “dtmp” bit (instead of “/tmp”) looks fishy and would suggest a
>> memory corruption, presumably in the daemon.
>
> The daemon used in the test, or the daemon used to do the package build?

The daemon under test (within the build environment).

>> I suppose the failure random, isn’t it?
>
> I ran it again, and I've got the same error:
>
> actual-error:
> + (srfi-34
> +   #<condition &nix-protocol-error [message: "path `dtmp/guix-tests/store/462z3fnl7bs44vp9s97jyg1z74nsfvly-tar' is not in the Nix store" status: 1] 1754ed0>)
>
> So that's either a very funny coincidence, or it's a structural problem.

It’s better if it’s not random.  :-)

> Do you have any suggestions for how I can debug this problem?

Assuming the failure also happens when you run “make check” outside the
build container (in the failed build tree), can you add ‘valgrind’ in
‘test-env’?  Specifically, in ‘test-env’, look for the line that invokes
‘./pre-inst-env guix-daemon’ and change it to ‘./pre-inst-env valgrind
guix-daemon’.

Ludo’.

  reply	other threads:[~2017-12-12 20:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 12:12 bug#29676: Guix test failure on tests/store Roel Janssen
2017-12-12 16:06 ` Ludovic Courtès
2017-12-12 16:50   ` Roel Janssen
2017-12-12 20:22     ` Ludovic Courtès [this message]
2017-12-20 13:11       ` Ludovic Courtès
2017-12-21 14:55         ` Roel Janssen
2017-12-21 15:01           ` Ludovic Courtès
2017-12-21 19:53             ` Roel Janssen
     [not found]             ` <87tvwkc9g1.fsf@gnu.org>
2017-12-22  9:24               ` Ludovic Courtès
2018-01-03 17:59                 ` Roel Janssen
2018-02-03  0:13                 ` Roel Janssen

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=871sjzitmm.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=29676@debbugs.gnu.org \
    --cc=roel@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 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).