Skip to content

Problem running codecov bitrise step (unable to find coverage files) #44

Closed
@kabirmahal

Description

@kabirmahal

Used Codecov (https://devcenter.bitrise.io/en/testing/measuring-your-code-coverage-with-codecov.html) with Bitrise after Xcode Test for iOS bitrise step has an issue where coverage isn't found. Below is the Codecov output. I know in the documentation it says .xcresults is not a valid output as Codecov only takes in xml or json. Does the codecov managed bitrise step not manage this for us? Would I need to write a custom script to encode the xcresults into a different format?

+------------------------------------------------------------------------------+
| (6) Codecov                                                                  |
+------------------------------------------------------------------------------+
| id: codecov                                                                  |
| version: 3.3.3                                                               |
| collection: https://github.com/bitrise-io/bitrise-steplib.git                |
| toolkit: bash                                                                |
| time: 2024-07-03T00:15:02Z                                                   |
+------------------------------------------------------------------------------+
|                                                                              |
gpg: directory '/Users/vagrant/.gnupg' created
gpg: /Users/vagrant/.gnupg/trustdb.gpg: trustdb created
gpg: key 806BB28AED779869: public key "Codecov Uploader (Codecov Uploader Verification Key) <[email protected]>" imported
gpg: Total number processed: 1
gpg:               imported: 1
gpg: Signature made Mon Apr 15 15:25:16 2024 GMT
gpg:                using RSA key 27034E7FDB850E0BBC2C62FF806BB28AED779869
gpg: Good signature from "Codecov Uploader (Codecov Uploader Verification Key) <[email protected]>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 2703 4E7F DB85 0E0B BC2C  62FF 806B B28A ED77 9869
codecov: OK
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   642    0   642    0     0   3847      0 --:--:-- --:--:-- --:--:--  3867
"version":"v0.7.3"
-Z -C 919ec72c3df83a4c506c131f7255f5f501e1673f
[2024-07-03T00:15:08.492Z] ['info'] 
     _____          _
    / ____|        | |
   | |     ___   __| | ___  ___ _____   __
   | |    / _ \ / _` |/ _ \/ __/ _ \ \ / /
   | |___| (_) | (_| |  __/ (_| (_) \ V /
    \_____\___/ \__,_|\___|\___\___/ \_/

  Codecov report uploader 0.7.3
[2024-07-03T00:15:08.566Z] ['info'] => Project root located at: /Users/vagrant/git
[2024-07-03T00:15:08.568Z] ['info'] ->  Token found by environment variables
[2024-07-03T00:15:08.630Z] ['info'] Searching for coverage files...
[2024-07-03T00:15:08.834Z] ['info'] Warning: Some files located via search were excluded from upload.
[2024-07-03T00:15:08.834Z] ['info'] If Codecov did not locate your files, please review https://docs.codecov.com/docs/supported-report-formats
[2024-07-03T00:15:08.834Z] ['error'] There was an error running the uploader: No coverage files located, please try use `-f`, or change the project root with `-R`
�[31;1mexit status 255�[0m
�[34;1mThis Step failed, but it was marked as "is_skippable", so the build continued.�[0m
|                                                                              |
+---+---------------------------------------------------------------+----------+
| �[33;1m!�[0m | �[33;1mCodecov (Failed)                                             �[0m | 7.22 sec |
+---+---------------------------------------------------------------+----------+
| Issue tracker: https://community.codecov.io                                  |
| Source: https://github.com/codecov/codecov-bitrise                           |

Metadata

Metadata

Labels

MediumMedium Priority Issues (to be fixed or re-evaluated in 3 monthsSupport

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions