unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Chris Marusich <cmmarusich@gmail.com>
Cc: 24060@debbugs.gnu.org
Subject: bug#24060: Test failure: tests/publish.scm
Date: Tue, 26 Jul 2016 23:08:35 +0200	[thread overview]
Message-ID: <871t2g150s.fsf@gnu.org> (raw)
In-Reply-To: <87r3ajs7p2.fsf@gmail.com> (Chris Marusich's message of "Sun, 24 Jul 2016 02:31:53 -0700")

Hello!

Chris Marusich <cmmarusich@gmail.com> skribis:

> test-name: /nar/gzip/*
> location: /home/marusich/guix/tests/publish.scm:163
> source:
> + (test-equal
> +   "/nar/gzip/*"
> +   "bar"
> +   (call-with-temporary-output-file
> +     (lambda (temp port)
> +       (let ((nar (http-get-port
> +                    (publish-uri
> +                      (string-append "/nar/gzip/" (basename %item))))))
> +         (call-with-gzip-input-port
> +           nar
> +           (cut restore-file <> temp)))
> +       (call-with-input-file temp read-string))))
> GET /nar/gzip/z8qsg9bmmjzgfi0bbgls1wxd0wmhhm2i-item
> expected-value: bar
> actual-value: #f
> actual-error:
> + (srfi-34
> +   #<condition &nar-error [file: "/tmp/guix-file.7fzEA2" port: #<closed: r6rs-custom-binary-input-port 0>] 27616f0>)
> result: FAIL

I fail to reproduce it with ‘make -j’ on my 4-core laptop.  Is it easy
to reproduce for you?

Does the zlib test always pass, as per:

  while make check TESTS=tests/zlib.scm ; do : ; done

?

Thanks,
Ludo’.

  parent reply	other threads:[~2016-07-26 21:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-24  9:31 bug#24060: Test failure: tests/publish.scm Chris Marusich
2016-07-24 23:01 ` Chris Marusich
2016-07-26 21:08 ` Ludovic Courtès [this message]
2016-07-27 10:49 ` Ludovic Courtès
2016-07-28 16:07 ` bug#24060: Test (tests/publish.scm) still fails after fix Chris Marusich
2016-07-28 21:20   ` Ludovic Courtès
2016-07-30  7:59     ` Chris Marusich
2016-07-30  9:16       ` Ludovic Courtès
2016-08-02 16:10       ` 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=871t2g150s.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=24060@debbugs.gnu.org \
    --cc=cmmarusich@gmail.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).