You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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. (actions/download-artifact#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.
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!
The text was updated successfully, but these errors were encountered: