Re: Updating python-pytest-cov
Hi Ben! On 10/28/21 11:19, Ben Greiner wrote:
Looks good to me so far. The test collection takes some time, botocore seems to have a huge test suite:
[ 72s] + pytest-3.9 --ignore=_build. --ignore=_build.python39 --ignore=_build.python38 -v [ 72s] ============================= test session starts ============================== [ 72s] platform linux -- Python 3.9.7, pytest-6.2.5, py-1.10.0, pluggy-1.0.0 -- /usr/bin/python3.9 [ 72s] cachedir: .pytest_cache [ 72s] rootdir: /home/abuild/rpmbuild/BUILD/botocore-1.22.3, configfile: pyproject.toml [ 124s] collecting ... collected 37177 items [ 124s] [ 125s] tests/functional/test_alias.py::test_can_use_alias[case0] PASSED [ 0%]
Yeah, but the overall result is negative, unfortunately: [ 2864s] = 234 failed, 36797 passed, 77 skipped, 243 warnings, 75 errors in 2850.65s (0:47:30) = [ 2872s] error: Bad exit status from /var/tmp/rpm-tmp.OvSRLF (%check) Seems like the tests in questions are online tests: [ 2864s] botocore.exceptions.EndpointConnectionError: Could not connect to the endpoint URL: "https://ec2.us-west-2.amazonaws.com/" [ 2864s] DEBUG botocore.retryhandler:retryhandler.py:185 Retry needed, action of: 1.399393024670891 [ 2864s] DEBUG botocore.endpoint:endpoint.py:262 Response received to retry, sleeping for 1.399393024670891 seconds Adrian
Am 28.10.21 um 12:13 schrieb John Paul Adrian Glaubitz:
Yeah, but the overall result is negative, unfortunately:
[ 2864s] = 234 failed, 36797 passed, 77 skipped, 243 warnings, 75 errors in 2850.65s (0:47:30) = [ 2872s] error: Bad exit status from /var/tmp/rpm-tmp.OvSRLF (%check)
Seems like the tests in questions are online tests:
[ 2864s] botocore.exceptions.EndpointConnectionError: Could not connect to the endpoint URL: "https://ec2.us-west-2.amazonaws.com/" [ 2864s] DEBUG botocore.retryhandler:retryhandler.py:185 Retry needed, action of: 1.399393024670891 [ 2864s] DEBUG botocore.endpoint:endpoint.py:262 Response received to retry, sleeping for 1.399393024670891 seconds
Adrian
Yeah, I see the current package before the upgrade only tests tests/unit in order to avoid that. The question is, whether these tests are meant to be tested against an online server or if there is a mock-server missing. If necessary, pytest has the nice feature to skip such tests with `-k "not (offendingtestA or offendigtestB)"` or even ignore complete paths with `--ignore`. Suggestion: https://build.opensuse.org/request/show/927934 %pytest --ignore tests/integration -k "not no_bare_six_import [ 881s] == 26510 passed, 74 skipped, 61 deselected, 242 warnings in 879.10s (0:14:39) == HTH, Ben
participants (2)
-
Ben Greiner
-
John Paul Adrian Glaubitz