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

"Run Test | Debug Test" repeated too many times #2666

Closed
ShivanshuKantPrasad opened this issue Sep 24, 2018 · 10 comments
Closed

"Run Test | Debug Test" repeated too many times #2666

ShivanshuKantPrasad opened this issue Sep 24, 2018 · 10 comments
Labels
area-testing bug Issue identified by VS Code Team member as probable bug windows

Comments

@ShivanshuKantPrasad
Copy link

Environment data

  • VS Code version: 1.27.2
  • Extension version (available under the Extensions sidebar): 2018.8.0
  • OS and version: Windows 10 Build 17760.1 (Insider)
  • Python version (& distribution if applicable, e.g. Anaconda): 3.7.0 (no distribution)
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
  • Relevant/affected Python packages and their versions: XXX

Actual behavior

image

Expected behavior

image

Steps to reproduce:

  1. When i open my project and run "Discover Test Files" it happens on this particular file
    Other test files work fine.

Logs

No output

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)

No output
@brettcannon brettcannon added bug Issue identified by VS Code Team member as probable bug area-testing info-needed Issue requires more information from poster labels Sep 24, 2018
@brettcannon
Copy link
Member

Can you share your setttings.json for your testing configuration and a code sample that reproduces the problem?

@ShivanshuKantPrasad
Copy link
Author

ShivanshuKantPrasad commented Sep 24, 2018

I uploaded the project directory to github.
This is the workspace settings.json file:

{
    "python.unitTest.pyTestEnabled": false,
    "python.unitTest.unittestEnabled": true,
    "python.unitTest.nosetestsEnabled": false,
    "python.unitTest.unittestArgs": [
        "-v",
        "-s",
        "./Tests",
        "-p",
        "*test.py"
    ]
}

This bug seems to happen in Tests/MaximumSubarray_test.py

@brettcannon brettcannon added needs verification and removed info-needed Issue requires more information from poster labels Sep 25, 2018
@brettcannon
Copy link
Member

Can you please verify, @d3r3kk ?

@d3r3kk
Copy link

d3r3kk commented Sep 28, 2018

Edit - comment placed in related, but incorrect item!

I cannot reproduce this exact behaviour on Windows nor on Linux. However, I do believe it to be related to #2660 and the registration of our callbacks on unittest projects.

I will continue to attempt to reproduce this behaviour going forward, but I've not yet seen this exact thing.

@brettcannon
Copy link
Member

@d3r3kk if you can't reproduce with the provided sample then I'm going to assume that we fixed this.

@d3r3kk
Copy link

d3r3kk commented Oct 2, 2018

Just got a repro today - but I am working on related issues that I believe all have the same root cause. Tracking this on #2660, but will reopen this as well to keep things specific.

@d3r3kk d3r3kk reopened this Oct 2, 2018
@d3r3kk d3r3kk added the windows label Oct 2, 2018
@d3r3kk
Copy link

d3r3kk commented Oct 2, 2018

I can only reproduce this in Windows, and @DonJayamanne didn't see any repro on macOS, so I'm limiting this to a windows-only issue.

@DonJayamanne
Copy link

@d3r3kk
Surprise surprise, I can't replicate this on Windows with Python 3.5 and 3.7

@d3r3kk
Copy link

d3r3kk commented Oct 3, 2018

Surprise surprise, I can't replicate this on Windows with Python 3.5 and 3.7

Interesting! I get it to repro consistently with a venv under python 3.7.

@luabud
Copy link
Member

luabud commented Sep 11, 2019

Closing as stale. If you still experience this issue, please file a new one. We refactored a lot of our test related code, so the underlying issue may have changed.

@luabud luabud closed this as completed Sep 11, 2019
@ghost ghost removed the needs PR label Sep 11, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Sep 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-testing bug Issue identified by VS Code Team member as probable bug windows
Projects
None yet
Development

No branches or pull requests

5 participants