Closed aelassas closed 4 years ago
I have been trying to reproduce the error locally myself by cloning your repository and setting using the same arguments you mentioned and a similar remote url as you mentioned in issue #79 .
Unfortunately I am unable to reproduce the error that you're seeing, as such I am forced to put this issue on hold until a later date.
@AdmiringWorm I've made Wexflow_coverage.xml available for you here: https://aelassas.github.io/wexflow/Wexflow_coverage.xml
I will try with that coverage, I do not believe it would make any difference though. But better safe than sorry.
I am afraid that I am still unable to reproduce the issue.
I did notice that the bash edition of codecov repeats the request some times, this may be one of the reason why it do that.
For now, I recommend that you use command where you set the slug yourself.
@AdmiringWorm Ok, thanks.
@AdmiringWorm uh question so I use codecov-exe 1.4.0 and I just started using it in github actions; is there a build yet that detects github actions now or no?
@AraHaan yes there is, the 1.8.0
version added support for github actions.
Do note though that you will still need to pass in the codecov token for it to actually be able to push the coverage reports to codecov.io.
EDIT: All release notes are available on the releases page where I will always add when support for a new CI is available.
alright thanks; but don't we need to like encrypt the token?
@AraHaan of course you would need to do that, which can be done under the Repository Settings -> Secrets section
Use the name CODECOV_TOKEN
as the environment variable name, and you don't even need to pass anything to codecov-exe yourself.
The drawback is obviously that this won't work on Pull Requests, but unfortunately there is no native support for github actions on codecov.io yet (due to missing information available in an action).
EDIT: It is possible that you will need to set the environment variable itself in the worflow yaml file.
env:
CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
Anyways, this is getting far off topic. Please reach out to me in the gitter channel if you got any more questions.
Alright thanks; got it working now.
@aelassas I know this is an old issue now, but if you still use codecov-exe
can you test if you are still seeing this error when using the latest version (1.11.2
was published a few moments ago).
Closing due to no response, assuming that the issue have been fixed.
When I try to upload the report with the version 1.7.0 using the command:
I get the following error;
But when I try to upload using --slug:
It succeeds after an error:
I'm using codecov.exe version 1.7.0 on windows 10 x64 from cmd.