From: David Bremner <david@tethera.net>
To: Floris Bruynooghe <flub@devork.be>, notmuch@notmuchmail.org
Subject: Re: [PATCH 2/2] python-cffi: returned OwnedMessage objects from Message.replies
Date: Tue, 11 Jan 2022 20:55:18 -0400 [thread overview]
Message-ID: <877db5zsax.fsf@tethera.net> (raw)
In-Reply-To: <87tuea9bid.fsf@powell.devork.be>
Floris Bruynooghe <flub@devork.be> writes:
> On Sun 09 Jan 2022 at 09:26 -0400, David Bremner wrote:
>> One thing I would like to think
>> about is the length of time it takes to run the pytests. It is not
>> currently the bottleneck in running the parallel tests for me, but it is
>> among the slower T*.sh. So it might be nice at some point to split into
>> several invocations for pytest, assuming multiple invocations of pytest
>> can run in parallel.
>
> There is the pytest-xdist plugin which is widely used and probably will
> work fine on the notmuch testsuite (I even contributed to the plugin at
> some point). It will split the workload between however many processes
> you choose, running them in parallel.
It sounds like it has potential, but I'm not sure how it would interact
with the existing scheme controlled by make. I suspect we'd end up with
too many processes/threads in total.
d
next prev parent reply other threads:[~2022-01-12 0:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-02 13:51 use after free in python notmuch2 bindings David Bremner
2022-01-07 13:06 ` David Bremner
2022-01-08 14:03 ` [PATCH 1/2] test: add known broken tests for recursive traversal of replies David Bremner
2022-01-08 14:03 ` [PATCH 2/2] python-cffi: returned OwnedMessage objects from Message.replies David Bremner
2022-01-08 18:59 ` Floris Bruynooghe
2022-01-09 13:26 ` David Bremner
2022-01-11 22:02 ` Floris Bruynooghe
2022-01-12 0:55 ` David Bremner [this message]
2022-01-09 13:27 ` [PATCH 1/2] test: add known broken tests for recursive traversal of replies David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877db5zsax.fsf@tethera.net \
--to=david@tethera.net \
--cc=flub@devork.be \
--cc=notmuch@notmuchmail.org \
/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://yhetil.org/notmuch.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).