Open webknjaz opened 2 weeks ago
@codecovdesign see above ^
I have this same use case. I test my code on various OS and python versions and tag each upload with two flags, one for OS and one for python version. The documentation warns against this: but I don't really understand the warning.
My expectation is that
Actually, on nth thought, maybe this is a weird way to do things. Maybe it's weird to include all python versions under the "windows" flag. Probably better to make compound flags like windows-3.12
instead of double flags like windows
and 3.12
.
Describe the bug
My typical setup is to add flags that correspond to the current runtime/OS/Python version and testing type (
pytest
vs.MyPy
). The uploads are coming from multiple jobs in the matrix on each CI run. This helps me distinguish between what env/tool covered which lines.Here's a message that shows up in red under each upload:
Both the action and cli still document this as supported: https://github.com/codecov/codecov-action#arguments / https://github.com/codecov/codecov-cli#do-upload.
The CI log shows that the invocation includes multiple
-F
options: https://github.com/ansible/awx-plugins/actions/runs/11672508220/job/32501323212?pr=52#step:23:61. This is no different from how it worked before. The change is in how the web service displays data now.Environment (please complete the following information):
GHA but shouldn't be important.
To Reproduce
Expected behavior
There should not be any message implying that marking uploads with multiple flags is incorrect.
Screenshots
An example of this can be seen @ https://app.codecov.io/github/ansible/awx-plugins/commit/3cd6520e2e0fd211366a5b91d509577a5d588bc0.
Additional context
Specific configuration example: https://github.com/ansible/awx-plugins/blob/3cd6520/.github/workflows/reusable-tox.yml#L394-L405