Skip to content
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

Debugging test with subprocesses does not work #4525

Closed
karthiknadig opened this issue Feb 25, 2019 · 4 comments

Comments

@karthiknadig
Copy link
Member

commented Feb 25, 2019

  1. Clone and open ptvsd folder.
  2. wait for the tests for load in the test explorer.
  3. Hit debug test on any of the tests.
@DonJayamanne

This comment has been minimized.

Copy link

commented Feb 26, 2019

Need to enable subProcess when debugging.
Works with that, but requires extension changes.

screen shot 2019-02-26 at 12 13 39 am

@DonJayamanne DonJayamanne changed the title Debugging test using test explorer or 'Debug Test' does not work Debugging test with subprocesses does not work Apr 15, 2019

@zchrissirhcz

This comment was marked as off-topic.

Copy link

commented May 19, 2019

Hi, how's the issue and patch going? I'm debugging a multiprocessing program, and I've tried python3.5, python3.6 and python3.7. All of these three version python failed when debugging in VSCode. I wonder if this can be fixed soon? Correct me if I'm wrong, thanks.

@DonJayamanne

This comment was marked as off-topic.

Copy link

commented May 19, 2019

Hi, how's the issue and patch going? I'm debugging a multiprocessing program, and I've tried python3.5, python3.6 and python3.7.

Please could you create a separate issue m this issue is used to track subprocess debugging in tests.

@DonJayamanne DonJayamanne added this to the 2019 - May Sprint 11 milestone May 29, 2019

@DonJayamanne DonJayamanne self-assigned this May 30, 2019

@karrtikr karrtikr self-assigned this May 31, 2019

@ericsnowcurrently

This comment has been minimized.

Copy link
Member

commented Jun 6, 2019

I was able to validate the fix by following the 3 steps above.

@pvscbot pvscbot removed the needs PR label Jun 6, 2019

@ericsnowcurrently ericsnowcurrently removed their assignment Jun 6, 2019

@lock lock bot locked as resolved and limited conversation to collaborators Jun 13, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.