-
Notifications
You must be signed in to change notification settings - Fork 2
Description
First, thanks for taking over the extension!
I tried it on my workspace, where the source code is in one "folder" and my tests are in another (so I can have different intellisense rules for test code and for source code, it's not a great solution, but it's better than having them mixed).
When I try to discover my tests, the extension will complain that the project.yml
file can't be found in one of the folders. This is correct, as one of them doesn't have any config files, but it could be maybe better handled with a warning or catching the exception? This is the output
2025-10-14 16:55:05.196 [error] Failed to read YAML file 'c:\Users\mundo\Workspace\RTOSSystemController\Test\project.yml': [Error: ENOENT: no such file or directory, open 'c:\Users\mundo\Workspace\RTOSSystemController\Test\project.yml'] {
errno: -4058,
code: 'ENOENT',
syscall: 'open',
path: 'c:\\Users\\mundo\\Workspace\\RTOSSystemController\\Test\\project.yml'
}
2025-10-14 16:55:05.643 [error] Ceedling failed to run in the configured shell. Please check if you can run `ceedling summary` in your shell.
Please check the ceedlingExplorer.shellPath option.
EXCEPTION: Could not find project filepath c:/Users/mundo/Workspace/RTOSSystemController/test/project.yml from command line argument
For historic reasons, my project.yml
is in the root of the project, not in tests, but the error would be the same in a more traditional project where project.yml
is located in tests
, and the src
folder doesn't have any Ceedling config.
As a side effect, the extension also complains that Ceedling failed to run in the configured shell
but I think it's an artifact of the fact that I don't have a project.yml
in that folder. My shell can run Ceedling, and the extension works for the folder that is correctly setup.