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

Error: "Failed to get workspace folder from test" #154199

Closed
amgodoi opened this issue Jul 5, 2022 · 3 comments
Closed

Error: "Failed to get workspace folder from test" #154199

amgodoi opened this issue Jul 5, 2022 · 3 comments
Assignees
Labels
*caused-by-extension Issue identified to be caused by an extension triage-needed

Comments

@amgodoi
Copy link

amgodoi commented Jul 5, 2022

Does this issue occur when all extensions are disabled?: Yes/No

  • VS Code Version: 1.68.1 and 1.69.0 (from source files)
  • OS Version: Ubuntu 22.04

image

Steps to Reproduce:

  1. Open folder with existing maven project
  2. Run Unit Test with Junit 4

I am able to run tests calling "mvn test" from terminal, but inside vscode occurs "Failed to get workspace folder from test" error.

@rebornix
Copy link
Member

rebornix commented Jul 5, 2022

Please file this issue against the Java extension, thanks!

@rebornix rebornix added the *caused-by-extension Issue identified to be caused by an extension label Jul 5, 2022
@vscodenpa
Copy link

This issue is caused by an extension, please file it with the repository (or contact) the extension has linked in its overview in VS Code or the marketplace for VS Code. See also our issue reporting guidelines.

Happy Coding!

@amgodoi
Copy link
Author

amgodoi commented Jul 5, 2022

Hi,

I have found this issue:
#74104

This is a vscode issue, but the problem is system dialog dependent. If I use the file dialog to open file, then "workspaceFolder" is wrong. But if i call vscode from command line (code .), then "workspaceFolder" is correct.

I will call from command line as a workaround ... work.

@github-actions github-actions bot locked and limited conversation to collaborators Aug 19, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*caused-by-extension Issue identified to be caused by an extension triage-needed
Projects
None yet
Development

No branches or pull requests

3 participants