-
Notifications
You must be signed in to change notification settings - Fork 11
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
GitHub Codecov v1 action freezes jobs when uploading report #354
Comments
@sbidoul can you try using |
@thomasrockhu-codecov Yes, we are migrating to v4, this solves the issue. However it would be nice if v1 would just fail instead of blocking, as this quickly fills the runners queue, and ends up blocking our whole GitHub org. |
@sbidoul yeah I understand that. |
@thomasrockhu-codecov The problem is not that v1 does not work any more. If it would simply fail, that would be totally fine and people would notice quickly that they need to upgrade. The problem is that it blocks, leading to very long actions queues congestion. That is not a friendly way to sunset a endpoint used from GitHub actions. |
@sbidoul hmm, I just ran To just manage expectations, if this is a problem specific to |
@sbidoul ok, I did some digging and I think I found the issue on our side. If you want to continue using v1, I strongly suggest adding a token to upload. However, we will work to make a fix for this. |
Thanks a lot for investigating @thomasrockhu-codecov To be clear we are migrating to v4 (with which we have no issues, just to confirm), but we have a long tail of v1 on older branches and open PRs.
Hard to tell for sure, but it is very prevalent. |
Describe the bug
I'm contacting you on behalf of the Odoo Community Association.
Since this morning, all our CI jobs are stuck in
codecov/codecov-action@v1
stepA typical stuck job log looks like this:
Environment (please complete the following information):
GitHub actions
Expected behavior
codecov-actions steps should fail or succeed but not remain pending "forever".
The text was updated successfully, but these errors were encountered: