We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I tried running the py.test tests in PyCharm and test_pdb_collection_failure_is_shown() from the test_pdb.py module simply hangs and stops execution.
PyCharm disables output capturing (probably because they want to capture it themselves).
It can be easily reproduced without PyCharm:
py.test -s testing/test_pdb.py
Then one can type 'c' (continue in pdb) - even though no output is shown regarding pdb - and the test run finishes.
Following is the default command executed by PyCharm to run the test:
python3 /opt/pycharm-community-4.5.2/helpers/pycharm/pytestrunner.py -p pytest_teamcity testing/test_pdb.py --capture=sys
To verify that the problem is as described TWO things need to be done:
--capture=sys
--capture=fd
args.append("-s") if "-s" not in args else None
This issue was originally reported/discussed on the mailing list.
Other info (probably not relevant):
The text was updated successfully, but these errors were encountered:
Bump.
Has anyone else experienced this or fixed this?
It's hanging for me too and it's driving me nuts.
Sorry, something went wrong.
im not aware of a core dev using pycharm - and as far as i can tell the pycharm integration breaks things there
Actually, I use PyCharm. 😁
But I recall someone fixing running testing/test_pdb.py with -s recently. Which pytest version does this happen?
testing/test_pdb.py
-s
I'll give it a go and report back.
Closing for now; we will be happy to re-open this once we get more information.
No branches or pull requests
I tried running the py.test tests in PyCharm and test_pdb_collection_failure_is_shown() from the test_pdb.py module simply hangs and stops execution.
PyCharm disables output capturing (probably because they want to capture it themselves).
It can be easily reproduced without PyCharm:
Then one can type 'c' (continue in pdb) - even though no output is shown regarding pdb - and the test run finishes.
Following is the default command executed by PyCharm to run the test:
To verify that the problem is as described TWO things need to be done:
--capture=sys
from the command (or replace with--capture=fd
)args.append("-s") if "-s" not in args else None
This issue was originally reported/discussed on the mailing list.
Other info (probably not relevant):
The text was updated successfully, but these errors were encountered: