unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org, 25177@debbugs.gnu.org
Subject: Re: python-tests: python-oslosphinx fixed. Please evaluate.
Date: Tue, 21 Feb 2017 08:50:03 +0100	[thread overview]
Message-ID: <87h93oyod0.fsf@elephly.net> (raw)
In-Reply-To: <20170221041645.GC19762@jasmine>


Leo Famulari <leo@famulari.name> writes:

> On Mon, Feb 20, 2017 at 12:00:21AM +0100, Marius Bakke wrote:
>> Danny Milosavljevic <dannym@scratchpost.org> writes:
>> > @Leo: Can you please start a new evaluation of python-tests?
>> 
>> I pushed some other fixes recently and built most of `guix package -A
>> python`, so I think we're ready for a new evaluation. I suggest we do a
>> new evaluation on 'master' after fixing the most critical packages so we
>> can include this in 'core-updates'. How does that sound?
>
> I just started a new evaluation of the branch.
>
>> These packages are known to fail still:
>> 
>> python-dendropy
>> python2-fastlmm
>> python2-bandit
>> python-openid
>> python-axolotl
>> 
>> + Many of the python2 variants of the openstack family libraries (oslo
>> etc), which seems to have a unittest2 version mismatch. Should be
>> easy to fix, but let's get some substitutes first :-)
>
> I think we should set '#:tests? #f' in these packages and build and
> merge the branch.
>
> If these remaining test suite failures indicate that the packages are
> broken, they will be equally broken with the test suites disabled. But
> overall we will benefit from fixing this bug in python-build-system.

I agree.

Only two tests (out of 820) for python-dendropy fail:

+ test_fixed_species_tree_fitting (dendropy.test.test_multispeciescoalescent.MultispeciesCoalescentBasicTestCase)
+ test1 (dendropy.test.test_multispeciescoalescent.MultispeciesCoalescentFixedSingleTreesCalculationTestCase)

Both fail with

    TypeError: unorderable types: Edge() < Edge()

I think it’s worth building the package anyway after disabling these two
tests.  I reported the test failures upstream:

    https://github.com/jeetsukumaran/DendroPy/issues/77

-- 
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  reply	other threads:[~2017-02-21  7:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-18 17:18 python-tests: python-oslosphinx fixed. Please evaluate Danny Milosavljevic
2017-02-19 23:00 ` Marius Bakke
2017-02-21  4:16   ` Leo Famulari
2017-02-21  7:50     ` Ricardo Wurmus [this message]
2017-02-21 17:30       ` Ricardo Wurmus
2017-02-21 17:47         ` bug#25177: " Leo Famulari
2017-02-21 22:15           ` Ricardo Wurmus
2017-02-22 12:42             ` Ricardo Wurmus
2017-02-22 12:57               ` Marius Bakke
2017-02-21 22:21           ` Ben Woodcroft

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=87h93oyod0.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=25177@debbugs.gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).