-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
4.3.0: pytest is failing in tests/test_all.py::DNSTest::test_custom_resolvconf
unit
#186
Comments
Then a number of the tests will simply fail. The test suite creates real DNS traffic. |
So it would be good to |
The test suite does not use pytest, it currently uses the vanilla unittest module. I'd take a PR improving things here, but as it stands if you are interested in running the tests you need Internet access. |
Correctly written unittest test suite can be handled by pytest. |
PRs are welcome. I currently don't have the time or energy to see if pytest would just work and add decorate functions. If you'd like to send a PR I'd be happy to review it. |
I'm packaging your module as an rpm package so I'm using the typical PEP517 based build, install and test cycle used on building packages from non-root account.
python3 -sBm build -w --no-isolation
build
with--no-isolation
I'm using during all processes only locally installed modulescut off from access to the public network
(pytest is executed with-m "not network"
)Module si build with PYCARES_USE_SYSTEM_LIB=1.
Here is pytest output:
Here is list of installed modules in build env
The text was updated successfully, but these errors were encountered: