unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Eric Bavier <ericbavier@centurylink.net>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 33284@debbugs.gnu.org
Subject: [bug#33284] [PATCH] python: Honor '--cores=...' in tests.
Date: Tue, 6 Nov 2018 19:22:37 -0600	[thread overview]
Message-ID: <20181106192237.79683848@centurylink.net> (raw)
In-Reply-To: <87o9b2p56m.fsf@fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]

On Tue, 06 Nov 2018 17:00:01 +0100
Marius Bakke <mbakke@fastmail.com> wrote:

> Eric Bavier <ericbavier@centurylink.net> writes:
> 
> > Hello Mathieu,
> >
> > On Tue, 6 Nov 2018 14:07:47 +0900
> > Mathieu Othacehe <m.othacehe@gmail.com> wrote:
> >  
> >> Hi Eric,
> >> 
> >> Your patch seems go to me, even if I think the root cause of your problem
> >> is fixed by:
> >> 
> >> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=33186#26
> >> 
> >> I think that both could be applied to core-updates.  
> >
> > Thanks for the link; it looks like it should help.  But, yes, I think
> > both can be applied.  
> 
> Note that the broken test has already been removed on 'core-updates'.
> 
> Eric: can you push a 'python-updates' branch?  I wonder if we have time
> for a "half-rebuild" before the next 'core-updates' round; I've got some
> other heavy-impact patches in my pipeline (Glib, Cairo, ++).
> 
> The patch LGTM.

Sure, I can push this to a new branch.  Thanks for the review.

`~Eric

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-11-07  1:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06  2:23 [bug#33284] [PATCH] python: Honor '--cores=...' in tests Eric Bavier
2018-11-06  5:07 ` Mathieu Othacehe
2018-11-06 14:52   ` Eric Bavier
2018-11-06 16:00     ` Marius Bakke
2018-11-07  1:22       ` Eric Bavier [this message]
2018-11-07  2:18         ` Eric Bavier
2018-11-17  6:45       ` bug#33284: " Eric Bavier

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=20181106192237.79683848@centurylink.net \
    --to=ericbavier@centurylink.net \
    --cc=33284@debbugs.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 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).