[issue31201] module test that failed doesn't exist

R. David Murray added the comment: Yep, I figured that. That's why I suggested the clarification to the README, if someone wants to generate a PR for it. -- ___ Python tracker

[issue31201] module test that failed doesn't exist

Paulo Matos added the comment: Argh, apologies David. I hadn't noticed the mistake. I simply copy/pasted and was expecting the command line to rerun all the tests that had previously failed. I was assuming the suite had some kind of state that recorded the tests that previously failed and ran

[issue31201] module test that failed doesn't exist

R. David Murray added the comment: Replace "test_that_failed" with the name of the test that failed. The README could be improved by saying: If any tests fail, you can re-run the failing test(s) in verbose mode. For example if, 'test_os' and 'test_gdb' failed, you can run:: make test TE

[issue31201] module test that failed doesn't exist

New submission from Paulo Matos: Trying to rerun the tests that failed but it just says that the module doesn't exist. I am running the exact command line mentioned in the readme file: $ make test TESTOPTS="-v test_that_failed" running build running build_ext The following modules found by det