Open AaronFontaine-DojoFive opened 8 months ago
Hope this can help : I had something similar and was also using gcov plugin. My gcov was configured with :
:gcov:
:xml_report: FALSE
Changing this to :
:gcov:
:xml_report: TRUE
Fixed the issue in my case. Maybe you can remove gcov to check ? I guess gcov default value is FALSE ?
I got this to work. The trick is to add a section for the xml_test_report
plugin that defines the location of the xml report artifact.
:xml_tests_report:
:artifact_filename: report_xunit.xml
You need that in addition to listing xml_tests_report
in the list of enabled plugins.
I didn't have to do anything in the section for the :gcov:
plugin. I'm not sure how that it got it working for you.
Thank you for contributing and posting a solution. The code which print the given error message is pretty simple.
I don't understand how adding a :xml_tests_report:
section in project.yml
fixed anything but I'm happy you found a workaround.
I am trying to get this to work natively in Windows 10. I am testing this with the temp sensor demo:
ceedling example temp_sensor
. Ceedling works from the command line. I can doceedling test:all
and see that all 47 tests pass. I have addedxml_tests_report
to the plugins list but the extension is still unhappy. I don't know how to debug this further.VS Code: 1.85.0 Ceedling: 0.31.1 Ruby: 2.7.3p183
Contents of the project.yml file:
The XML report exists and is generated to
build/artifacts/test/report.xml
. If I delete the build directory and try to use the extension, I get this error without anything even being generated. It is somehow preemptively and incorrectly deciding it cannot run ceedling. If I run ceedling from the command line, the build directory is regenerated including thereport.xml
file.Here is the error in VS Code.![image](https://github.com/numaru/vscode-ceedling-test-adapter/assets/92054065/b2f2a1b6-573f-4ff7-a309-e1f9445cc090)