-
Notifications
You must be signed in to change notification settings - Fork 33
False positives using when using pytest-xdist -f (--looponfail) #85
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
Comments
Thanks for the excellent repro steps! 💯 The problem seems to have been introduced in 0.6.0 (#79) 🤔 |
I did notice that I was passing both the source file and the test file to
pytest but I think I was able to reproduce when only passing the test file.
I will get back to you on that.
…On Sun, Apr 12, 2020, 17:17 David Tucker ***@***.***> wrote:
Thanks for the excellent repro steps! 💯
The problem seems to have been introduced in 0.6.0 (#79
<#79>) 🤔
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#85 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABORVLM2V5ZGUMKNUNLAR63RMIVVFANCNFSM4MGQ6OJA>
.
|
Can confirm error occurs even if ran properly:
|
When a test fails, pytest --verbose --mypy ::mypy
|
Would you mind cutting a release with this? I would love to have this working. |
When doing TDD, after the first mypy error, the plugin start emitting errors on collection.
It will continue normally until you hit an actual mypy fail, then in the follow round (after mypy error is fixed) this warning is emitted forever until pytest is killed and restarted.
Steps to Reproduce (assumes python 3.8 and pipenv available):
mkdir ~/tmp20200412
cd ~/tmp20200412
git clone git@bitbucket.org:y2kbugger/test_driven_development_by_example_tdd_follow_along.git
cd ./test*
git checkout b0a2f56
pipenv sync
pipenv shell
pytest --mypy -f money.py test_money.py
In another terminal:
cd ~/tmp20200412/test*
echo 'lol: str = 2' >> money.py
git checkout b0a2f56 -- .
Note I kill with keyboard interrupt here:
Then everything goes fine again:
The text was updated successfully, but these errors were encountered: