-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Cannot restart test debugger (i.e. shift-cmd-F5) with "purpose"==["debug-test"] #17636
Comments
"purpose" is something that's handled entirely by the VSCode Python extension, including the validation logic that gets tripped here; moving the issue accordingly. |
@tclose I will leave this item open to clarify that bit in the description for "debug-test" |
I think the scenario here is that the session is started via the Test Explorer, but then restarted (while it's still running) via Run -> Restart Debugging. |
@karthiknadig thanks for the response but I am referring to the case that @int19h suggested. With the old test explorer plugin I was using and the deprecated "request": "test" launch configuration it was possible to restart a running test (i.e. using the green "recycle" arrow in the debugging controls) |
I see. Thanks for clarifying. |
Has anyone found a way to make this work again ? |
Fixed via #18290 |
/verified Works for me as long as I don't have a launch.json with a test config in it. Although maybe I just setup the test config incorrectly. |
Sorry, not sure whether this is a bug report or feature request
Environment data
[Clang 12.0.0 (clang-1200.0.32.29)] on darwin, built by Homebrew
Version: 1.60.2
Commit: 7f6ab5485bbc008386c4386d08766667e155244e
Date: 2021-09-22T11:59:27.195Z (1 wk ago)
Electron: 13.1.8
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Darwin x64 19.6.0
Actual behavior
When debugging a pytest unit test in the test explorer with the following launch configuration
I am not able to restart the debugger using the debug controls (e.g. shift-cmd-F5) and receive the following message
Expected behavior
The debugging session is refreshed and the test run again
Steps to reproduce:
The text was updated successfully, but these errors were encountered: