-
Notifications
You must be signed in to change notification settings - Fork 124
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
[BUG] Code coverage is failing to upload on dependabot PRs #755
Comments
For context: This was the last time the action completed successfully: https://github.com/opensearch-project/opensearch-js/actions/runs/8635756121/job/23674229038
We recently upgraded to cocodecov-action from v2 to v4 because of a different error: https://github.com/opensearch-project/opensearch-js/actions/runs/8635655002/job/23674115308
|
Both errors (v2 and v4) pointed to missing token. Most likely related to the breaking changes on codecov According to this FAQ, a token is required for our use case, and it can be found at https://app.codecov.io/github/opensearch-project/opensearch-js/settings. However I don't have access to that page or the github settings page of this repo to update the workflow with a token. Going to try OIDC first. |
How did we configure it in other repos? |
Dashboards is using codecov-action@v3 |
It doesn't work for dashboards either: https://github.com/opensearch-project/OpenSearch-Dashboards/actions/runs/8693296132/job/23839779862 |
But that will hide the failure? :) We want code coverage don't we, or am I missing something? |
This step is only uploading codecoverage to codecov.com to track code-coverage overtime. The steps that runs code coverage and assure that the coverage clears a certain threshold still pass. |
So uploading for PRs doesn't and shouldn't work? We should turn that off explicitly rather than ignoring failures because it will hide future real failures quietly. |
It used to work. It's a nice-to-have-feature. If we have the time we should go through the trouble of adding the token for it. I think for now we can just remove it like you said. |
What is the bug?
How can one reproduce the bug?
See PRs, e.g. #753 (review)
https://github.com/opensearch-project/opensearch-js/actions/runs/8685364111/job/23814712885?pr=753
What is the expected behavior?
Coverage to run and upload.
The text was updated successfully, but these errors were encountered: