Skip to content

Conversation

vstinner
Copy link
Member

@vstinner vstinner commented Sep 25, 2023

When a test fails with "env changed" and --rerun option is used, the test is now re-run in verbose mode in a fresh process.

When a test fails with "env changed" and --rerun option is used, the
test is now re-run in verbose mode in a fresh process.
@vstinner
Copy link
Member Author

I wrote this change to debug issue gh-109832:

Warning -- sys.stderr was modified by test.test_concurrent_futures.test_deadlock
Warning --   Before: <_io.TextIOWrapper name='<stderr>' mode='w' encoding='utf-8'>
Warning --   After:  <_io.StringIO object at 0x3ff971b6410>

build: https://buildbot.python.org/all/#/builders/75/builds/895

@vstinner vstinner merged commit 72fb39c into python:main Sep 25, 2023
@vstinner vstinner deleted the regrtest_rerun_env_changed branch September 25, 2023 14:21
csm10495 pushed a commit to csm10495/cpython that referenced this pull request Sep 28, 2023
When a test fails with "env changed" and --rerun option is used, the
test is now re-run in verbose mode in a fresh process.
Glyphack pushed a commit to Glyphack/cpython that referenced this pull request Sep 2, 2024
When a test fails with "env changed" and --rerun option is used, the
test is now re-run in verbose mode in a fresh process.
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.

1 participant