From: Chris Marusich <cmmarusich@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 24060@debbugs.gnu.org
Subject: bug#24060: Test (tests/publish.scm) still fails after fix
Date: Sat, 30 Jul 2016 00:59:49 -0700 [thread overview]
Message-ID: <8737mrr1xm.fsf@gmail.com> (raw)
In-Reply-To: <87r3ajs7p2.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
ludo@gnu.org (Ludovic Courtès) writes:
> Is this new failure systematic, or does it occur randomly?
I've tried running the test over 100 times, and it failed every time.
I've also tested it in a QEMU guest running GuixSD, and it still fails.
I will see if I can reproduce it on a totally different physical
computer and get back to you.
> What version of Guile do you use?
The version is "guile (GNU Guile) 2.0.11". This version comes from
running "guix environment guix".
I just now tried the same tests using guile-next (which is version
2.1.2), and they still failed.
> I wonder if this could be a remnant of <http://bugs.gnu.org/19610>.
> Does commenting out the “/nar/gzip/*” test hide the problem?
Commenting out that test-equals section did not hide the problem.
> If so, does the patch below help?
I tried the patch anyway, and unfortunately the test still failed.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-07-30 8:01 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
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 [this message]
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=8737mrr1xm.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=24060@debbugs.gnu.org \
--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 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).