all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric Bavier <bavier@member.fsf.org>
To: David Thompson <dthompson2@worcester.edu>
Cc: guix-devel@gnu.org
Subject: Re: Test failure cpan
Date: Fri, 20 Feb 2015 15:55:25 -0600	[thread overview]
Message-ID: <20150220155525.20feec4d@PocketWee> (raw)
In-Reply-To: <87a908b781.fsf@fsf.org>

On Fri, 20 Feb 2015 16:31:26 -0500
David Thompson <dthompson2@worcester.edu> wrote:

> Andreas Enge <andreas@enge.fr> writes:
> 
> > Hello,
> >
> > I just ran a "make check", and got a failure in the cpan test. Here is the
> > cpan.log:
> >
> > accepted connection from pid 9095, uid 1000
> > spurious SIGPOLL
> > 415 operations
> > accepted connection from pid 9095, uid 1000
> > 1 operations
> > %%%% Starting test cpan  (Writing full log to "cpan.log")
> > tests/cpan.scm:63: FAIL cpan->guix-package
> > # of unexpected failures  1
> > ;;; note: source file ./srfi/srfi-64.scm
> > ;;;       newer than compiled /gnu/store/zjhaqhfbwkh5n4cbsrk8h7bg8yqrimls-guile-2.0.11/lib/guile/2.0/ccache/srfi/srfi-64.go
> > FAIL tests/cpan.scm (exit status: 1)
> >
> > I suppose it is related to the recent changes by Eric on the perl
> > import.
> 
> Mark just pushed a patch that fixes a 'guix pull' issue caused by the
> CPAN importer.  Perhaps the tests will pass now?
> 

I hope it fixes the 'guix pull' issue, but I don't think it will fix
the test failure.  I'm updating the test and will push a fix soon.  My
last commits changed the behavior of how module dependencies are
handled, and I failed to update the results that the test expects. 

Sorry about the mess.

`~Eric

  reply	other threads:[~2015-02-20 21:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 17:45 Test failure cpan Andreas Enge
2015-02-20 21:31 ` David Thompson
2015-02-20 21:55   ` Eric Bavier [this message]
2015-02-20 22:01   ` Andreas Enge

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=20150220155525.20feec4d@PocketWee \
    --to=bavier@member.fsf.org \
    --cc=dthompson2@worcester.edu \
    --cc=guix-devel@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.