Closed Frank-D closed 1 year ago
Thanks for the issue @Frank-D, there is also extra logging you can grab to help us triage your issue. (see gif in link below)
https://github.com/ryanluker/vscode-coverage-gutters/issues/228#issuecomment-524641795
Can you also confirm that the jococo.xml file is in the workspace folder somewhere as well?
Thanks @ryanluker for your quick response and additional details!
For an odd reason, I let the extension on the side for a little while after submitting this issue and kept coding, and at some point, I had to go back to the java class file to check something, and suddenly, it was all highlighted of green/red/yellow lines (mostly of green : P) hourray!
Unfortunately, I have absolutely no idea whatsoever how it happened, I don't recall playing at all with any config since I filed that issue and kept coding random java code until it worked randomly some hours later....so I won't be able to help anyone having the same issue with this ticket I'm sorry..
Anyhow, happy ending, and this extension is amazing keep on the great work! ; -)
Hi! Another "coverage file not found" issue, I'm sorry! 😆
I'm not sure what to describe in particular, other than:
jococo.xml
code coverage report properly generated.I tried playing with all the settings I saw perhaps relevant (
coverage-gutters.coverageFileNames
,coverage-gutters.manualCoverageFilePaths
,coverage-gutters.coverageBaseDir
andcoverage-gutters.coverageReportFileName
) with different mix and match of configs (different file names, different relative and absolute paths, etc), but no luck.I was at some point able to get a vs code warning notification in the bottom-right corner generated by the extension to display an error message telling me that it couldn't find my coverage file, but the funny thing is, whenever I was actually fixing the path to my jococo.xml report file, then the message disappeared and back to the no notification behaviour where I only get the watch link to spin and then show as "No Coverage", which is telling me that it seems like it's probably actually finding my report file with all the default settings, but crashing perhaps trying to read it?
Not sure if there's a location/log somewhere that I could open and see how this extension is doing, e.g. 1) is it finding my coverage file yes or no, and 2) if yes, then what's the error that is perhaps causing the extension to crash trying to process my coverage file...?