-
Notifications
You must be signed in to change notification settings - Fork 74
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
1.6.0: pytest is failing in pooch/tests/test_core.py::test_check_availability_on_ftp
unit
#331
Comments
Hi @kloczek. Thanks for opening this issue and sorry for the delayed reply. The test function you are trying to run will fail because the UNAVCO ftp server was decommissioned. We already merged #322 to solve it. I imagine that you are packaging the latest release of Pooch and this is blocking you from doing it. If you are in a rush, I would recommend ignoring this error: it's not due to a bug in our code as pointed out in that PR. If you want to have full tests pass, I think we are about to release a Pooch version soon, considering that we fixed a few bugs recently. |
Units which requires public network acces should be marked by |
Thanks for the tip. Pooch currently uses the BTW, Pooch v.1.7.0 have been just released, which includes the fixes introduced in #322. I think now you shouldn't have any problem running the test locally (while connected to internet). |
I've opened #367 to double check that all network-accessing tests are properly marked. That seems to be the real issue here so closing this one. |
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 modulesHere is pytest output:
Here is list of installed modules in build env
The text was updated successfully, but these errors were encountered: