From: ar-jan <ar-jan@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: python3-curio-1.4
Date: Mon, 08 Feb 2021 19:06:29 +0100 [thread overview]
Message-ID: <20210208180629.qVIyPkPlTuYlPKd8tOBMobeT-fyv435fADtprCE1I14@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28419@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 888 bytes --]
New comment by ar-jan on void-packages repository
https://github.com/void-linux/void-packages/pull/28419#issuecomment-775336386
Comment:
OK, will do.
I thought the new dependencies might have to be added in separate pull requests because there was no way to proceed with the the original #28272 and find out which specific package was at issue.
> To test things, send them to your own fork.
I wanted to see CI test results for individual packages because it seemed there were no other options to find out what was going on. Are CI tests possible on individual forks, or what do you mean by testing?
> Here, failure in CI is because container have some privileges that https://github.com/dabeaz/curio/blob/1.4/tests/test_network.py#L317 don't expect - please disable that one test with pytest -k.
Aha! Any way I could have discovered that? There were no errors or warnings.
next prev parent reply other threads:[~2021-02-08 18:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 22:49 [PR PATCH] " ar-jan
2021-02-02 22:59 ` [PR PATCH] [Updated] " ar-jan
2021-02-08 14:26 ` ar-jan
2021-02-08 15:32 ` ar-jan
2021-02-08 15:40 ` ar-jan
2021-02-08 17:40 ` Chocimier
2021-02-08 17:40 ` [PR PATCH] [Closed]: " Chocimier
2021-02-08 18:06 ` ar-jan [this message]
2021-02-08 18:06 ` ar-jan
2021-02-08 18:19 ` Chocimier
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=20210208180629.qVIyPkPlTuYlPKd8tOBMobeT-fyv435fADtprCE1I14@z \
--to=ar-jan@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).