From: bobertlo <bobertlo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: aws-cli: update to 1.22.23 (with deps)
Date: Sun, 12 Dec 2021 13:49:33 +0100 [thread overview]
Message-ID: <20211212124933.zuqY4xLS7bTnnt78AHypc56uqlKoYVXw_dlHR1yhFoY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34490@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
New comment by bobertlo on void-packages repository
https://github.com/void-linux/void-packages/pull/34490#issuecomment-991892684
Comment:
> > ```
> > # pytest marked deprecated, suggests using tox (which does not test against system packages)
> > ```
>
> Where exactly is this comment from? They migrated to pytest in september, so I would assume it's not already deprecated.
When I got the tests running with their deps installed and pytest it still says:
```
WARNING: Testing via this command is deprecated and will be removed in a future version. Users looking for a generic test entry point independent of test runner are encouraged to use tox
```
The Tox tests install their own python3-venv and download package dependencies with pip.
@dotnetfox the tests will run but give that warning message and I did find that code you mentioned as well as figure out all the dependencies. I think they have some proprietary secret sauce going on with these tests. I got the test failures down to like 300-ish (out of ~30,000) and they were all saying invalid AWS credentials.
I spent a decent chunk of time on two different nights trying to get these tests to run.
next prev parent reply other threads:[~2021-12-12 12:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-12 3:35 [PR PATCH] Aws 2112 bobertlo
2021-12-12 5:17 ` aws-cli: update to 1.22.23 (with deps) uhohspaghetios
2021-12-12 8:43 ` dotnetfox
2021-12-12 11:33 ` paper42
2021-12-12 12:49 ` bobertlo [this message]
2021-12-12 13:44 ` paper42
2021-12-12 13:46 ` paper42
2021-12-12 13:54 ` paper42
2021-12-12 13:54 ` paper42
2021-12-12 18:02 ` [PR PATCH] [Updated] " bobertlo
2021-12-12 18:08 ` bobertlo
2021-12-12 20:50 ` [PR REVIEW] " paper42
2021-12-12 20:50 ` paper42
2021-12-12 20:50 ` paper42
2021-12-12 23:14 ` [PR PATCH] [Updated] " bobertlo
2021-12-12 23:21 ` bobertlo
2021-12-12 23:45 ` [PR PATCH] [Merged]: " paper42
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=20211212124933.zuqY4xLS7bTnnt78AHypc56uqlKoYVXw_dlHR1yhFoY@z \
--to=bobertlo@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).