all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: Guix-devel <guix-devel@gnu.org>, Alex Kost <alezost@gmail.com>,
	Federico Beffa <beffa@ieee.org>
Subject: Re: [PATCH] import: Move beautify description from cran to utils. (was Re: [PATCH 6/6] gnu: Add emacs-slime.)
Date: Thu, 14 Jan 2016 22:15:33 +1000	[thread overview]
Message-ID: <56979165.2080304@uq.edu.au> (raw)
In-Reply-To: <idjbn8oflei.fsf@bimsb-sys02.mdc-berlin.net>



On 14/01/16 21:30, Ricardo Wurmus wrote:
> Ben Woodcroft <b.woodcroft@uq.edu.au> writes:
>
>> On 14/01/16 20:31, Ricardo Wurmus wrote:
>>> This breaks two of the cran importer tests:
>>>
>>> (test-equal "beautify-description: use double spacing"
>>>     "This is a package.  It is great.  Trust me Mr.  Hendrix."
>>>     ((@@ (guix import cran) beautify-description)
>>>      "This is a package. It is great. Trust me Mr. Hendrix."))
>>>
>>> (test-equal "beautify-description: transform fragment into sentence"
>>>     "This package provides a function to establish world peace"
>>>     ((@@ (guix import cran) beautify-description)
>>>      "A function to establish world peace"))
I just tested these with "make check" and also by ./pre-inst-env guile 
tests/cran.scm, and they seem to pass. Am I doing something incorrectly?

However, ironically tests/gem fails.
>>> How about moving these tests elsewhere?  (Or should they be removed?)
>> Ah, sorry. Should they be moved to a new file tests/import-utils? Why do
>> you suggest that they should be removed?
> I don’t have any preference for a name.  “tests/import-utils” sounds
> good to me.  If we can keep (and later enhance) the tests it would
> obviously be better.  (I just meant that I wouldn’t be too sad if they
> were removed for whatever reasons.)
>
> Would you like to submit a patch to add tests/import-utils (including
> adding it to SCM_TESTS in Makefile.am) and move these two test cases
> there?
Happy to provide a patch fixing the gem test, and moving the (failing?) 
cran tests to this new file since even if they pass that is a more 
appropriate place for them. It'll be the weekend before I have time for 
this though, apologies for leaving master broken.

ben

  reply	other threads:[~2016-01-14 12:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30 17:33 [PATCH 6/6] gnu: Add emacs-slime Federico Beffa
2015-12-31  0:55 ` Ben Woodcroft
2015-12-31  9:12   ` Federico Beffa
2016-01-05 22:17     ` Ludovic Courtès
2016-01-09 10:30       ` Federico Beffa
2016-01-09 15:27         ` Alex Kost
2016-01-09 18:45         ` Ludovic Courtès
2015-12-31  9:52   ` Ricardo Wurmus
2015-12-31 23:52     ` Alex Kost
2016-01-01  8:25       ` Ricardo Wurmus
2016-01-01  8:35         ` Ben Woodcroft
2016-01-01 15:04           ` Ricardo Wurmus
2016-01-05 14:25             ` [PATCH] import: Move beautify description from cran to utils. (was Re: [PATCH 6/6] gnu: Add emacs-slime.) Ben Woodcroft
2016-01-10 21:17               ` Ludovic Courtès
2016-01-14  9:49                 ` Ben Woodcroft
2016-01-14 10:31                   ` Ricardo Wurmus
2016-01-14 10:53                     ` Ben Woodcroft
2016-01-14 11:30                       ` Ricardo Wurmus
2016-01-14 12:15                         ` Ben Woodcroft [this message]
2016-01-17  1:00                           ` [PATCH] import: Move beautify description from cran to utils Ben Woodcroft
2016-01-18  9:45                             ` Ludovic Courtès
2016-01-20 22:13                               ` Ben Woodcroft
2016-01-21  8:51                                 ` Ludovic Courtès
2015-12-31 10:17 ` [PATCH 6/6] gnu: Add emacs-slime Alex Kost
2015-12-31 10:32   ` Federico Beffa
2015-12-31 20:40     ` Alex Kost
2015-12-31 10:33 ` Alex Kost

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=56979165.2080304@uq.edu.au \
    --to=b.woodcroft@uq.edu.au \
    --cc=alezost@gmail.com \
    --cc=beffa@ieee.org \
    --cc=guix-devel@gnu.org \
    --cc=ricardo.wurmus@mdc-berlin.de \
    /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.