Error: No coverage files located

Description

Codecov fails to locate .coverage file. If specified with the -f flag, it reports “There was an error processing coverage reports.” The coverage reports are generated via pytest-cov, and build succeeds. This started happening after a PR was merged yesterday.

(xxx) hawk31@xps:~/xxx$ pytest --cov=xxx --cov-config=.coveragerc tests/
============================================== test session starts ==============================================
platform linux -- Python 3.7.4, pytest-6.2.4, py-1.10.0, pluggy-0.13.1
rootdir: /home/hawk31/xxx
plugins: codecov-0.3.0, cov-2.12.1
collected 10 items 

[...]

========================================= 10 passed in 96.68s (0:01:36) =========================================

Commit SHAs

Private GitHub repo.

Repository

Private Github repo.

CI/CD or Build URL

The issue happens both locally and via GitHub actions using the new codecov uploader.

Uploader

./codecov -t {token}

Codecov Output

(xxx) hawk31@xps:~/xxx$ ./codecov -t weqweqew

     _____          _
    / ____|        | |
   | |     ___   __| | ___  ___ _____   __
   | |    / _ \ / _` |/ _ \/ __/ _ \ \ / /
   | |___| (_) | (_| |  __/ (_| (_) \ V /
    \_____\___/ \__,_|\___|\___\___/ \_/

  Codecov report uploader 0.1.0
=> Project root located at: /home/hawk31/xxx
Error!: Error: No coverage files located, please try use `-f`, or change the project root with `-R`

Any idea of what could be happening? I apologize for not being able to share the repository.

Many thanks in advance

@josejimenezluna can you specify a recent commit SHA where this happens?

@tom @josejimenezluna

What was the actual solution here, because I’ve got the same error on an upload step;

@marksweb can you make a new ticket for this? I can take a look today

1 Like

I’m having this issue as well. It’s also not causing my github actions workflow to fail which I think it should give that it’s throwing an error.

@bcaddy also can you make a new ticket?

Done. Thanks for your help

Hi @bcaddy apologies I meant here in the community boards.

Ahh, that makes sense. Will do

1 Like