Coverage is not reported after v0.1.19
Closed this issue · 5 comments
We don't get coverage reports after updating to v0.1.19 (which starts using v2 API). It seems like uploading is OK but the coverage is never reported. Thanks.
_____ _
/ ____| | |
| | ___ __| | ___ ___ _____ __
| | / _ \ / _\`|/ _ \/ __/ _ \ \ / /
| |___| (_) | (_| | __/ (_| (_) \ V /
\_____\___/ \__,_|\___|\___\___/ \_/
Ruby-0.1.19
==> Circle CI detected
==> Gzipping contents
==> Uploading reports
url: https://codecov.io
query: token=secret&flags&service=circleci&build=3107&job=0&slug=org%2Frepo&pr&branch=dependabot%2Fbundler%2Fcodecov-0.1.19&commit=896963cf4b95d4ed4cdf2b683af8389780486709
-> Uploading to Codecov
https://codecov.io//upload/v2?token=secret&flags&service=circleci&build=3107&job=0&slug=org%2Frepo&pr&branch=dependabot%2Fbundler%2Fcodecov-0.1.19&commit=896963cf4b95d4ed4cdf2b683af8389780486709
View reports at https://codecov.io/github/org/repo/commit/896963cf4b95d4ed4cdf2b683af8389780486709
Same here
Here is latest PR without updated codecov
ONLYOFFICE-QA/telegram-github-changes-bot#143
There is codecov report as comment in this PR
This is a bump of codecov iteself and no report as comment
ONLYOFFICE-QA/telegram-github-changes-bot#144
I have a strange HTML response at all:
0.1.18
- refactor and move to use v2 endpoint
I think, such breaking changes should be in minor version of zero-major, like 0.2.0
. I'm locking at patch-version, and without any changes in Bundle it just stops to work.
0.1.18
is also broken:
Failure/Error: require 'codecov'
LoadError:
cannot load such file -- colorize
# /usr/local/bundle/gems/codecov-0.1.18/lib/codecov.rb:7:in `require'
# /usr/local/bundle/gems/codecov-0.1.18/lib/codecov.rb:7:in `<top (required)>'
# ./spec/spec_helper.rb:9:in `require'
# ./spec/spec_helper.rb:9:in `<top (required)>'
It's fixed here and not in the Changelog: 10b2ef1
So, 'codecov', '~> 0.1.0', '< 0.1.18'
helps.
Hi all, this was clearly a huge mishap on my part. We should not have released the version without testing more thoroughly. We have released 0.1.20
which should patch the issue with the migration to v2. Apologies again and thank you for your patience.