-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[CLI v0.6.0] XML file being treated as a directory. #439
Comments
@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: 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 |
👍 thanks @maxwell-legrand. this is on me, I'll work on a fix |
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. |
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: