-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v2 not finding python .coverage file #577
Comments
As a workaround, does running But see also #456 where it's unclear if that's now necessary with v2 or not... |
Yes, that workaround helps. So the thing is that with v1, it used to work with Regarding documentation:
That's also why I specified v2 in the title of this issue - though it seems that I forgot to mention that it used to work with v1 without converting the output to some other format. So my suggestions are to either:
|
Interestingly, I am still using v1 and have my coverage report stored in
It used to be located automatically but I had to add |
I'm going to close this out as the answer is to run |
Hi all,
I have a multi-language repository and for some reason, the v2 action can't find the python coverage reports. Here's my setup:
./temp
, they put the coverage reports thereHere's how I invoke the action:
The exact error message is this:
Note that I specified the
temp/
folder containing the coverage reports. I use the same bind clause for all languages, meaning that their output is put into the same folder (though on machines since they are part of different matrix entries, thus they don't interfere with each other). I know that this directory is correct because it is working just fine for my JS tests, which put their test output in there, too....I've also checked the output by adding the following step just before calling the
codecov
action:The output I get for this is:
So the coverage file is definitely there.
Now why does this work for my JS reports, but not for the
.coverage
file generated by my python tests?coverage/lcov.info
.coverage
(I've also tried moving it into acoverage
subdirectory, to mimic the structure by the JS reports)The text was updated successfully, but these errors were encountered: