3.1.2 fails to find Xcode coverage files
#16
Comments
|
Hi @ncreated, just out of curiosity, have you been able to get this to work previously? |
Hi @thomasrockhu-codecov 馃憢. No, we were not using Codecov before. We are adding this integration now, but struggling with above issue. What works fine is using deprecated Bash uploader directly in our repo (without using |
|
@ncreated would you be able to supply the output of the |
Turns out I made a try with
Bitrise log from uploading with However, then I tried customizing this codecov report by leveraging I can see in this log that |
|
@ncreated looping this into codecov/uploader#223, sorry for the delay in getting back a response to you. |
|
Hi folks, anybody else still experiencing this? We've had Codecov tool disabled since leak this past year and I wanted to check if this step was still supported? I'm using latest XcodeTest for iOS (4.x.x), CodeCov (3.x.x) If I look at my artifacts, I see:
|
|
I'm a bit out of the loop because we're trying to use Codecov for the first time today, but it seems like the new uploader (used by 3.x of this step) does not support Xcode, and the old uploader (2.x) was deprecated this month. Do I understand correctly that this means that we can't use the step for iOS projects? Is there an intermediate solution? |
|
@liamnichols, to summarize, 3.x doesn't yet support Xcode but is being worked on by the team currently. A possible solution is to run something like swift package generate-xcodeproj
xcodebuild -scheme CombineCloudKit-Package -destination 'id=529F3FC8-EB55-4644-A1B3-01FF1DA6A2BA' -resultBundlePath foo.xcresult -enableCodeCoverage YES test
cd ../xcode-poc/
node generate-codecov-json.js --archive-path ../CombineCloudKit/foo.xcresult/from this comment before the step. |
|
@thomasrockhu Do you have an progress update for this? |
|
@callumboddy-collecting sorry I don't have a solid update. I'm hoping that we'll have something by EOM |
|
@thomasrockhu-codecov all good, thank you. looking forward to getting this integration up and running. |
|
@callumboddy-collecting we released a new version of the underlying uploader that hopefully makes some progress here. you should be able to add I'm not particularly well-versed in xcode development nor bitrise, but if I can help and/or if your project is public, I'd like to be involved with making sure it works fo ryou. |
|
Hi @thomasrockhu-codecov, thanks for the update. I'll give this a go and get back to you. Our repo is private. |
|
Hey, @thomasrockhu-codecov your solution works. Thanks! The only issue I have with it is the processing time. However, when I added -v (verbose) flag into other flags, I found it did go through each source file to convert. If I do it via solution from here it takes 8 minutes only. Is there any way to optimize this conversion process? |
|
For future references who struggle to make it work - add it to |
|
@holyavkin I'm going to try to make an improvement to the step so that it doesn't have to be as clunky as the |
|
@holyavkin I don't want to lose track of the comment you wrote about longer processing times. Are you able to share logs in this community post |
|
Closing this issue as it seems to be resolved |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
馃憢 We're using
3.1.2to upload coverage data from our project. After running tests withxcode-test, thecodecov-bitrisefails with:I expect that running
codecovstep afterxcode-teststep (withgenerate_code_coverage_files: 'yes') should be enough to have coverage data uploaded to codecov.io. Instead, it fails even in minimal setup.It is very much unclear to me how to proceed further, as for what I see the
codecov-bitrisestep uses the new uploader, which unlike the old, and deprecated bash uploader does not support Xcode coverage files. There seems to be nothing I can do to address the error, unless I write my own exporter of Xcode coverage data to the format that works with the new uploader 馃槥.How can we use
codecov-bitrisestep to find and upload our Xcode coverage data?Our setup in
bitrise.yml:Important part of the CI log:
The text was updated successfully, but these errors were encountered: