v4 upgrade - can't get coverage to show up - unusable report error about codecov-action HOT 13 OPEN

Thoughts?

from codecov-action.

@ldemailly taking a look

from codecov-action.

@ldemailly my apologies - This dropped of my radar!

@thomasrockhu @drazisil-codecov can you help out here?

from codecov-action.

@thomasrockhu-codecov

from codecov-action.

@ldemailly, apologies, I'm not quite understanding the issue right now. Is it that when you bump to v4 that you are getting an unusable report error?

We have since made some changes to the underlying CLI, would you be able to try it again?

from codecov-action.

I changed how I gather coverage, I used to do it package by package this way:

#!/usr/bin/env bash

set -e
echo "" > coverage.txt
rm -f profile.out

for d in $(go list ./... | grep -v vendor); do
    echo "### Working on package coverage $d"
    go test -coverprofile=profile.out -covermode=atomic $d
    if [ -f profile.out ]; then
        cat profile.out >> coverage.txt
        rm profile.out
    fi
done

and maybe that was creating the mix up above, or you fixed something because now it works with my simpler/more direct coverage

This being said... I'd rather not have to change a dozen repos to add

        token: ${{ secrets.CODECOV_TOKEN }}

why is that now (in v4) needed for public repos?

from codecov-action.

@thomasrockhu-codecov Retried worked (past that 502) but now back to "unusable report"

info - 2024-02-09 20:45:56,383 -- Your upload is now processing. When finished, results will be available at: https://app.codecov.io/github/fortio/fortio/commit/88cbb9365d06f05d152266366aff6846ed9c98d9

https://api.codecov.io/upload/gh/fortio/fortio/download?path=v4/raw/2024-02-09/C0DD8D0DDF23CE2B21C69976960C6C9E/88cbb9365d06f05d152266366aff6846ed9c98d9/c98b1e47-8fe3-48f2-8434-f8de0d2b9115/1ff1743d-3047-49cc-8650-c28256fdab22.txt

from codecov-action.

ping? https://app.codecov.io/gh/fortio/fortio/commits dropped to 0% as a result

from codecov-action.

Another one despite using 4.0.2 of the action:

https://app.codecov.io/github/fortio/fortio/commit/a3a4496ae4f8dfc42ba9577d49f44537f00a30aa

seems the issue is a mix of plain text and compressed coverage in the report:

from codecov-action.

same with 4.1.0 https://app.codecov.io/github/fortio/fortio/commit/360913cefff2af7482c1dba8e7a545ee08aba8d4

from codecov-action.

ps: wanted to downgrade to v3 meanwhile but getting

[2024-03-06T12:12:34.707Z] ['error'] There was an error running the uploader: Error uploading to https://codecov.io: Error: There was an error fetching the storage URL during POST: 404 - {'detail': ErrorDetail(string='Could not find a repository associated with upload token ***', code='not_found')}

my CODECOV_TOKEN works with v4 (well however much v4 works)

from codecov-action.

removing the token (!) v3 finally passed and the format is quite different

https://storage.googleapis.com/codecov/v4/raw/2024-03-06/C0DD8D0DDF23CE2B21C69976960C6C9E/a6470bfeeca554f3c0a1bc170e2b983e745ae5a0/fae2be97-0801-4022-8304-745edfe2e296.txt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=GOOG1EJOGFN2JQ4OCTGA2MU5AEIT7OT5Z7HTFOAN2SPG4NWSN2UJYOY5U6LZQ%2F20240306%2FUS%2Fs3%2Faws4_request&X-Amz-Date=20240306T123514Z&X-Amz-Expires=30&X-Amz-SignedHeaders=host&X-Amz-Signature=a4ae6280754605346bb714aa29535b398d27d38dde88b2e4d9257029f6d2a277

I hope v3 will stay working very long and v4 is fixed as well (including token weirdness) - thanks @rohan-at-sentry

from codecov-action.

@rohan-at-sentry I hope everything is ok with you - any update?

from codecov-action.