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

Exception following VSCode startup after following Getting Started instructions #713

Closed
itbgcthate opened this issue Jul 19, 2019 · 4 comments
Labels
Feature: configure more info needed More info is needed from the community for us to properly triage and investigate.

Comments

@itbgcthate
Copy link

Reference issue #701, "Error: spawn ctest ENOENT", closed by the initiator.
Reference issue #522, "Stuck with 'Configuring project: Saving open files'", open.

I'm opening a new issue because #701 was closed by the initiator without a description for how it was mitigated. Issue #522 appears to be common to a number of situations.

I get the following exception after restarting VSCode when following instructions in the Getting Started document during initial setup. Everything configures and builds fine until VSCode is restarted.

[rollbar] Unhandled exception: Unhandled Promise rejection: Post-folder-open Error: spawn ctest ENOENT {"folder":{"uri":{"$mid":1,
"fsPath":"c:\Users\Me\Documents\Projects\Embedded\VSCode\MyProject","_sep":1,
"external":"file:///c%3A/Users/Me/Documents/Projects/Embedded/VSCode/MyProject",
"path":"/c:/Users/Me/Documents/Projects/Embedded/VSCode/MyProject","scheme":"file"},
"name":"MyProject","index":0}}

It seems to be having a problem with the definition of "external".

@lyk7539511
Copy link

lyk7539511 commented Aug 14, 2019

Same issue, have you worked out any approach to solve the problem?
[rollbar] Unhandled exception: Unhandled Promise rejection: Post-folder-open Error: spawn ctest ENOENT {"folder":{"uri":{"$mid":1,
"fsPath":"d:\Master\CPP","_sep":1,
"external":"file:///d%3A/Master/CPP",
"path":"/d:/Master/CPP",
"scheme":"file"},
"name":"CPP","index":0}}
@itbgcthate

@itbgcthate
Copy link
Author

I have not.

@emanspeaks
Copy link
Contributor

Are you both using MinGW by chance? Make sure that CTest is on your system PATH, and then do a Scan for Kits. There's a bug with MinGW kits that it saves off your PATH variable when you do a scan, so if CTest was not on the path at the time you first scanned, it will not find CTest subsequently when using that kit. See #760.

@bobbrow
Copy link
Member

bobbrow commented Apr 13, 2020

Is this still an issue? We made some fixes to MinGW scenarios recently and would ask that you try again. If it is still an issue, can you please provide instructions for how to reproduce the problem? (e.g. a repository to clone, and which version of CMake and MinGW you are using.)

Thank you!

@bobbrow bobbrow closed this as completed Apr 13, 2020
@bobbrow bobbrow added the more info needed More info is needed from the community for us to properly triage and investigate. label Apr 13, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Jan 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Feature: configure more info needed More info is needed from the community for us to properly triage and investigate.
Projects
None yet
Development

No branches or pull requests

4 participants