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
2.2.0: pytest (7.2) is failing in two units #491
Comments
Related to #487. |
Thanks, this was fixed in #494. |
IMO it is really bad looking hack 😋 + PYTHONPATH=/home/tkloczko/rpmbuild/BUILDROOT/python-cloudpickle-2.2.0-4.fc35.x86_64/usr/lib64/python3.8/site-packages:/home/tkloczko/rpmbuild/BUILDROOT/python-cloudpickle-2.2.0-4.fc35.x86_64/usr/lib/python3.8/site-packages
+ /usr/bin/pytest -ra -m 'not network'
==================================================================================== test session starts ====================================================================================
platform linux -- Python 3.8.16, pytest-7.2.1, pluggy-1.0.0
rootdir: /home/tkloczko/rpmbuild/BUILD/cloudpickle-2.2.0, configfile: tox.ini
collected 256 items
tests/cloudpickle_file_test.py .......
tests/cloudpickle_test.py ................................................................................................................................................................................................................s.................................
tests/test_backward_compat.py .......
================================================================================== short test summary info ==================================================================================
SKIPPED [1] tests/cloudpickle_test.py:2261: Need Pickle Protocol 5 or later
============================================================================== 255 passed, 1 skipped in 15.36s ============================================================================== |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 modulesLooks like
cloudpickle
test suite is failing with pytest 7.2.Here is pytest output:
Here is list of installed modules in build env
The text was updated successfully, but these errors were encountered: