-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
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
[test] Fail if coverage can't be push #13084
Conversation
a1594e4
to
46d4bd6
Compare
.circleci/config.yml
Outdated
fi | ||
- run: | ||
name: Coverage | ||
command: bash <(curl -s https://codecov.io/bash) -Z |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-Z
is the important change here.
What do you think of keeping the existing build steps? Because running the regression tests is an intensive task, we only do it once all the other tests are green. |
@oliviertassinari I only looked at the CI runtime but |
Sure, better keep it simple |
The coverage report could previously fail silently which could leave codecov in an indeterminate pending state. If the report fails now CI will also fail.
3e6a9af
to
fc1e45a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no clue what this option does, but I trust you with it. Do you have some documentation?
Ok, found it in https://codecov.io/bash
|
Well done! |
The coverage report could previously fail silently which could leave codecov in an infinite pending state. If the report fails now CI will also fail.
Since this didn't test anything that test:unit didn't test already I moved this to another job so that it doesn't block other jobs because of a simple network error.See codecov/codecov-bash#134