From: Eric Bavier <ericbavier@centurylink.net>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 33284-close@debbugs.gnu.org
Subject: bug#33284: [PATCH] python: Honor '--cores=...' in tests.
Date: Sat, 17 Nov 2018 00:45:15 -0600 [thread overview]
Message-ID: <20181117004515.1111b65a@centurylink.net> (raw)
In-Reply-To: <87o9b2p56m.fsf@fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1057 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.
I've pushed this to the core-updates-next branch in commit
5b01b6034aeab32a5011c5757f18bd9772d3497d
`~Eric
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-11-17 6:46 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
2018-11-07 2:18 ` Eric Bavier
2018-11-17 6:45 ` Eric Bavier [this message]
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=20181117004515.1111b65a@centurylink.net \
--to=ericbavier@centurylink.net \
--cc=33284-close@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 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.