From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: New package: python3-pytest-xdist and dependencies
Date: Fri, 10 Jun 2022 03:44:24 +0200 [thread overview]
Message-ID: <20220610014424.f1eszobwqgUogvqfdgSmamF6xZfTJ30WrSigtDSCYL8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37099@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]
There's a merged pull request on the void-packages repository
New package: python3-pytest-xdist and dependencies
https://github.com/void-linux/void-packages/pull/37099
Description:
- New package: python3-execnet-1.9.0
- New package: python3-pytest-forked-1.4.0
- New package: python3-pytest-xdist-2.5.0
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
prev parent reply other threads:[~2022-06-10 1:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 6:13 [PR PATCH] " classabbyamp
2022-05-13 6:39 ` classabbyamp
2022-05-13 16:40 ` classabbyamp
2022-05-14 18:58 ` ahesford
2022-05-14 19:20 ` classabbyamp
2022-05-14 19:21 ` classabbyamp
2022-05-14 19:25 ` [PR PATCH] [Updated] " classabbyamp
2022-05-14 20:29 ` tornaria
2022-05-17 17:05 ` [PR PATCH] [Updated] " classabbyamp
2022-05-17 19:45 ` [PR REVIEW] " basploeger
2022-05-17 19:51 ` basploeger
2022-05-17 20:35 ` classabbyamp
2022-05-28 6:55 ` [PR PATCH] [Updated] " classabbyamp
2022-06-05 13:05 ` basploeger
2022-06-07 15:23 ` [PR PATCH] [Updated] " classabbyamp
2022-06-07 15:27 ` classabbyamp
2022-06-09 22:49 ` [PR REVIEW] " jcgruenhage
2022-06-09 22:52 ` jcgruenhage
2022-06-09 22:53 ` classabbyamp
2022-06-09 22:53 ` classabbyamp
2022-06-09 22:54 ` jcgruenhage
2022-06-09 22:57 ` [PR PATCH] [Updated] " classabbyamp
2022-06-09 22:58 ` [PR REVIEW] " jcgruenhage
2022-06-10 1:44 ` ahesford [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=20220610014424.f1eszobwqgUogvqfdgSmamF6xZfTJ30WrSigtDSCYL8@z \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).