From: Leo Famulari <leo@famulari.name>
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org, 25177@debbugs.gnu.org
Subject: Re: python-tests: python-oslosphinx fixed. Please evaluate.
Date: Mon, 20 Feb 2017 23:16:45 -0500 [thread overview]
Message-ID: <20170221041645.GC19762@jasmine> (raw)
In-Reply-To: <87bmtxkcqi.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me>
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-02-21 4:16 UTC|newest]
Thread overview: 30+ 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 [this message]
2017-02-21 7:50 ` bug#25177: " Ricardo Wurmus
2017-02-21 7:50 ` Ricardo Wurmus
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-21 22:15 ` Ricardo Wurmus
2017-02-22 12:42 ` Ricardo Wurmus
2017-02-22 12:57 ` Marius Bakke
2017-02-22 12:57 ` Marius Bakke
2017-02-24 22:20 ` Marius Bakke
2017-02-24 22:29 ` Ricardo Wurmus
2017-02-24 22:36 ` Marius Bakke
2017-02-27 11:46 ` Marius Bakke
2017-02-27 20:20 ` Leo Famulari
2017-02-28 16:15 ` Marius Bakke
2017-03-01 15:36 ` Leo Famulari
2017-03-01 17:36 ` Marius Bakke
2017-03-01 17:44 ` Marius Bakke
2017-03-02 22:22 ` Leo Famulari
2017-03-02 23:31 ` Marius Bakke
2017-03-02 23:42 ` Leo Famulari
2017-03-03 16:52 ` Marius Bakke
2017-03-03 17:51 ` Leo Famulari
2017-02-21 22:21 ` Ben Woodcroft
2017-02-21 17:30 ` Ricardo Wurmus
2017-02-21 4:16 ` Leo Famulari
2017-02-19 23:00 ` Marius Bakke
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=20170221041645.GC19762@jasmine \
--to=leo@famulari.name \
--cc=25177@debbugs.gnu.org \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.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 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.