Skip to content

chore: fix issue if only run test_gitlab.py func test #2255

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

Merged
merged 2 commits into from
Aug 25, 2022
Merged

Conversation

JohnVillalovos
Copy link
Member

Make it so can run just the test_gitlab.py functional test.

For example:
$ tox -e api_func_v4 -- -k test_gitlab.py

Make it so can run just the test_gitlab.py functional test.

For example:
$ tox -e api_func_v4 -- -k test_gitlab.py
@JohnVillalovos JohnVillalovos changed the title chore: enable only test_gitlab.py func test chore: fix issue if only run test_gitlab.py func test Aug 24, 2022
@JohnVillalovos JohnVillalovos requested a review from nejch August 24, 2022 15:21
The GitHub CI is showing a ResourceWarning, causing our test to fail.

Update test to only look for our UserWarning which should not appear.

What was seen when debugging the GitHub CI:
{message:
    ResourceWarning(
        "unclosed <socket.socket fd=12, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=6, laddr=('127.0.0.1', 50862), raddr=('127.0.0.1', 8080)>"
    ),
    category: 'ResourceWarning',
    filename: '/home/runner/work/python-gitlab/python-gitlab/.tox/api_func_v4/lib/python3.10/site-packages/urllib3/poolmanager.py',
    lineno: 271,
    line: None
}
@nejch
Copy link
Member

nejch commented Aug 25, 2022

I've been checking the ResourceWarning topic in requests - and I think we should eventually make sure to get rid of it completely so I'd merge this for now to get the other PR in, and then later ensure a clean run without warnings in the test run and then potentially clean up if needed :)

@nejch nejch merged commit e095735 into main Aug 25, 2022
@nejch nejch deleted the jlvillal/noop branch August 25, 2022 12:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants