Skip to content

Conversation

@blueyed
Copy link
Contributor

@blueyed blueyed commented Jan 21, 2020

No description provided.

@blueyed blueyed force-pushed the fix-test_repr_traceback_with_invalid_cwd branch from 3219484 to bcd589b Compare January 21, 2020 19:24
@blueyed blueyed changed the title tests: fix test_repr_traceback_with_invalid_cwd [WIP] tests: fix test_repr_traceback_with_invalid_cwd Jan 21, 2020
@blueyed blueyed force-pushed the fix-test_repr_traceback_with_invalid_cwd branch from d5cf0a0 to 160aaa4 Compare January 24, 2020 11:21
@blueyed blueyed changed the title [WIP] tests: fix test_repr_traceback_with_invalid_cwd tests: fix test_repr_traceback_with_invalid_cwd Jan 24, 2020
This never worked as expected (since a912d37), and only py38-windows
triggered the mocked `os.getcwd` unintentionally, via `inspect`.
@blueyed blueyed force-pushed the fix-test_repr_traceback_with_invalid_cwd branch from 160aaa4 to 79ae86c Compare January 24, 2020 11:52
@blueyed blueyed merged commit 09ab5fd into pytest-dev:master Jan 24, 2020
@blueyed blueyed deleted the fix-test_repr_traceback_with_invalid_cwd branch January 24, 2020 22:41
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