Skip to content

Space in extension path: Debugger test failures #14166

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

Closed
rchiodo opened this issue Sep 29, 2020 · 1 comment
Closed

Space in extension path: Debugger test failures #14166

rchiodo opened this issue Sep 29, 2020 · 1 comment
Assignees
Labels
area-internal Label for non-user facing issues bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority

Comments

@rchiodo
Copy link

rchiodo commented Sep 29, 2020

  1. Unit Tests - debugging
    Debugger should start (nosetest):

    Incorrect number of test files

    • expected - actual

    -0
    +2

    at testStartingDebugger (out/test/testing/debugger.test.js:95:23)
    at processTicksAndRejections (internal/process/task_queues.js:94:5)
    at Context. (out/test/testing/debugger.test.js:126:9)

  2. Unit Tests - debugging
    Debugger should stop when user invokes a test discovery (nosetest):

    Incorrect number of test files

    • expected - actual

    -0
    +2

    at testStoppingDebugger (out/test/testing/debugger.test.js:132:23)
    at runMicrotasks ()
    at processTicksAndRejections (internal/process/task_queues.js:94:5)
    at Context. (out/test/testing/debugger.test.js:154:9)

  3. Unit Tests - debugging
    Debugger should not stop when test discovery is invoked automatically by extension (nosetest):

    Incorrect number of test files

    • expected - actual

    -0
    +2

    at testDebuggerWhenRediscoveringTests (out/test/testing/debugger.test.js:160:23)
    at runMicrotasks ()
    at processTicksAndRejections (internal/process/task_queues.js:94:5)
    at Context. (out/test/testing/debugger.test.js:190:9)

Steps to repro:

  1. Clone into a path with a space
  2. Run debugger tests

Or if that doesn't work, use a github action as done in this pr:
#14113

@rchiodo rchiodo added bug Issue identified by VS Code Team member as probable bug triage-needed Needs assignment to the proper sub-team important Issue identified as high-priority labels Sep 29, 2020
@karthiknadig karthiknadig added needs PR area-internal Label for non-user facing issues labels Sep 30, 2020
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Sep 30, 2020
@kimadeline kimadeline self-assigned this Oct 5, 2020
@kimadeline
Copy link

Didn't make any changes, couldn't repro on main 43a8716: https://github.com/kimadeline/vscode-python/actions/runs/290164499

image

@ghost ghost removed the needs PR label Oct 5, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-internal Label for non-user facing issues bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority
Projects
None yet
Development

No branches or pull requests

3 participants