Kin Numaru

Can you share the generated `.cpuprofile` file?

You should be able to see the output of the ceedling command in the `OUTPUT` panel by clicking on the test. Can you share this message? The report.xml seems legit...

Sorry for the late reply and thank you for taking the time to debug the issue. Do you use ruby code elsewhere in the project.yml? Do you really need those...

Great! I will let it as it is for now and keep the issue open.

Do you use the [ms-vscode-remote.remote-ssh](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-ssh) plugin? We faced the same issue with the WSL and the remote plugin was a workaround. Also, what is your ceedlingExplorer.shellPath option?

Unfortunately, there is no debug log nor unit tests for this extension. Here is how I debug: - First, I try to reproduce the problem with the vscode window opened...

As you might expect, I don't use ceedling and this extension anymore. But I still planned to do the work to support v1.0 when the release will be out. I...

I think the Test Explorer UI also added for us a translation layer. And `testExplorer.useNativeTesting: true` in the settings.json should enable the native experience. I didn't use vscode testing in...

Thank you for contributing and posting a solution. The code which print the given error message is pretty simple. https://github.com/numaru/vscode-ceedling-test-adapter/blob/4283fdf91f10a13a5208d8d8e67ea7070d3dd3a0/src/adapter.ts#L284-L293 I don't understand how adding a `:xml_tests_report:` section in `project.yml`...

This is a limitation of the child_process.exec nodejs api