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

Test explorer has no icons or buttons when using WSL remote #7151

Closed
karthiknadig opened this issue Aug 29, 2019 · 4 comments
Closed

Test explorer has no icons or buttons when using WSL remote #7151

karthiknadig opened this issue Aug 29, 2019 · 4 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster

Comments

@karthiknadig
Copy link
Member

Environment data

  • VS Code version: 1.37.1
  • Extension version (available under the Extensions sidebar): 2019.8.30787
  • OS and version: Windows/ WSL Ubuntu (bionic)
  • Python version (& distribution if applicable, e.g. Anaconda): 3.6
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
  • Relevant/affected Python packages and their versions: pytest
  • Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info How to update the language server to the latest stable version #3977): LS

Expected behaviour

Should be able to run tests from Test explorer and see the status of the tests

Actual behaviour

No status icons or buttons after test discovery.
image

Steps to reproduce:

  1. Clone this project: https://github.com/karthiknadig/multievent
  2. Open the workspace in WSL
  3. After test discovery is done, Run tests using the UI

Also Run current test file or the code lenses causes this error. This might be relevant.

============================= test session starts ==============================
platform linux -- Python 3.6.8, pytest-5.1.1, py-1.8.0, pluggy-0.12.0
rootdir: /mnt/c/GIT/multievent, inifile: pytest.ini
collected 20 items

tests/test_common.py ....................                                [100%]

--------------- generated xml file: /tmp/tmp-53x95u13c31Xjx.xml ----------------
============================== 20 passed in 0.18s ==============================
Error: TypeError: Cannot read property '$' of undefined
@karthiknadig karthiknadig added bug Issue identified by VS Code Team member as probable bug triage-needed Needs assignment to the proper sub-team labels Aug 29, 2019
@luabud
Copy link
Member

luabud commented Aug 29, 2019

The second error is related to #6990

@DonJayamanne
Copy link

Possibly a dup of microsoft/vscode#78651

@karrtikr karrtikr added the triage label Sep 3, 2019
@ghost ghost removed the triage-needed Needs assignment to the proper sub-team label Sep 3, 2019
@karrtikr karrtikr self-assigned this Sep 3, 2019
@karrtikr
Copy link

karrtikr commented Sep 3, 2019

@karthiknadig Please provide Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)

I expect to see something like,

open-change.svg:1 Failed to load resource: net::ERR_NOT_IMPLEMENTED
repl.svg:1 Failed to load resource: net::ERR_NOT_IMPLEMENTED
refresh.svg:1 Failed to load resource: net::ERR_NOT_IMPLEMENTED
debug.svg:1 Failed to load resource: net::ERR_NOT_IMPLEMENTED
run-tests.svg:1 Failed to load resource: net::ERR_NOT_IMPLEMENTED

If that is the case, this issue is a dup.

@karrtikr karrtikr added the info-needed Issue requires more information from poster label Sep 3, 2019
@karthiknadig
Copy link
Member Author

looks like with VSC 1.38.0 , and updated WSL this is fixed:
image

@ghost ghost removed the triage label Sep 5, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Sep 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

4 participants