unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Cyril Roelandt <tipecaml@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Python: disable test_wait_result() as it fails on some setups
Date: Mon, 07 Apr 2014 09:41:31 +0200	[thread overview]
Message-ID: <8761mlzivo.fsf@gnu.org> (raw)
In-Reply-To: <1396820010-19125-1-git-send-email-tipecaml@gmail.com> (Cyril Roelandt's message of "Sun, 6 Apr 2014 23:33:30 +0200")

Cyril Roelandt <tipecaml@gmail.com> skribis:

> * gnu/packages/patches/python-fix-tests.patch: disable a failing test.

Thanks!

What would you think of pushing an upgrade to 3.3.5 at the same time?

(Plus a MIPS fix or workaround, which Mark is looking at.)

Ludo’.

  parent reply	other threads:[~2014-04-07  7:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-27 23:07 0.6 is around the corner! Ludovic Courtès
2014-04-01 18:50 ` Mark H Weaver
2014-04-01 19:20   ` Mark H Weaver
2014-04-01 20:02     ` Ludovic Courtès
2014-04-01 19:25   ` Ludovic Courtès
2014-04-02 19:43     ` Mark H Weaver
2014-04-03 16:32       ` Python 3 test failures Ludovic Courtès
2014-04-03 17:11         ` Mark H Weaver
2014-04-03 19:51           ` Ludovic Courtès
2014-04-06 19:41     ` 0.6 is around the corner! Ludovic Courtès
2014-04-06 21:33       ` [PATCH] gnu: Python: disable test_wait_result() as it fails on some setups Cyril Roelandt
2014-04-07  6:17         ` Mark H Weaver
2014-04-07 22:13           ` [PATCH] gnu: Python: disable failing tests on MIPS64 Cyril Roelandt
2014-04-08  0:10             ` Mark H Weaver
2014-04-08  3:50               ` Mark H Weaver
2014-04-09  0:40               ` Nikita Karetnikov
2014-04-09  2:51                 ` Cyril Roelandt
2014-04-09 16:04                   ` Nikita Karetnikov
2014-04-07  7:41         ` Ludovic Courtès [this message]
2014-04-07 21:45         ` [PATCH] gnu: Python: disable test_wait_result() as it fails on some setups 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=8761mlzivo.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=tipecaml@gmail.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 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).