codecov-cli
codecov-cli copied to clipboard
codecov
[CLI v0.6.0] XML file being treated as a directory.
When using CLI v0.6.0 I'm running into an issue where XML files are being treated as directories. The XML files are Cobertura-style results being generated from the xcresultparser tool.
Reverting to version 0.5.2 of the CLI tool resolves the issue for me, however, I'd prefer to use the most up-to-date version if possible.
The files are definitely not related to the issue since I am able to download / open them and they are single files. This coupled with the fact that a reversion resolved the issue makes me believe that something in the v0.6.0 release may be causing the issue.
Thanks in advance for the assistance, and let me know if there is any more information I can provide!
@maxwell-legrand can you provide a link to CI for this? Would like to be able to repro
I'm unable to provide a direct link as the CI job was run inside an organization. I was able to identify some possible root causes:
https://github.com/codecov/codecov-cli/commit/4de8fc24b865bf71c9d6b3cac9b1379fafa11883
My understanding is the above commit changes how file searching worked. We were explicitly naming files as well as using file search, and with how the download-artifact action works it was wrapping the files in a folder with the same name. (https://github.com/actions/download-artifact/issues/141) For example, we would download my-coverage.xml but it would be in a folder with the same name (e.g, the file would be located at my-coverage.xml/my-coverage.xml) and the codecov cli detected both the file AND the directory which caused it to fail.
Hey there , just wanted to follow up on this and see if there have been any updates? Thanks!
@maxwell-legrand apologies I haven't gotten to this yet, thanks for pinging back, will prioritize.
@maxwell-legrand sorry this one got away from me. I've been trying to repro this for a bit, and I can't seem to get a directory to be expected as a file like my-coverage.xml/my-coverage.xml only pulls the file and not my-coverage.xml/ the directory. Are you still experiencing this?