-
-
Notifications
You must be signed in to change notification settings - Fork 440
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
FileNotFoundError while writing results against a test suite that modifies current working directory #824
Comments
I'm not entirely sure, but I'm suspicious that the test behaviour which triggers this is my use of the Click I use that here (and in a bunch of other places): https://github.com/simonw/datasette/blob/a9453c4dda70bbf5122835e68f63db6ecbe1a6fc/tests/test_publish_now.py#L118-L119 |
It looks like this bug is NOT unique to the 5.0 series. I ran
|
Something is in the air... this was fixed on master last week: #806 . I have no idea why it hasn't been reported before. |
Unfortunately I don't think it's fixed in master - I tried running against master by using the following:
Then running
|
Maybe this is a bug in |
Aha - maybe it's this bug over there: pytest-dev/pytest-cov#306 |
Describe the bug
When running 5.0a5 against my datasette project I get the following error at the end of the test run:
I'm pretty sure this is because some of my tests in that test suite mess around with the current working directory. It would be great if
coverage.py
was robust against changes made to the working directory.To Reproduce
These steps to reproduce work on my OS X laptop running Python 3.7:
The text was updated successfully, but these errors were encountered: