Skip to content
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

Closed
sbidoul opened this issue Apr 29, 2024 · 7 comments · Fixed by codecov/codecov-api#538
Closed

GitHub Codecov v1 action freezes jobs when uploading report #354

sbidoul opened this issue Apr 29, 2024 · 7 comments · Fixed by codecov/codecov-api#538
Assignees
Labels
Bug For issues and unexpected behaviors

Comments

@sbidoul
Copy link

sbidoul commented Apr 29, 2024

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 step

A typical stuck job log looks like this:

image

Environment (please complete the following information):

GitHub actions

Expected behavior

codecov-actions steps should fail or succeed but not remain pending "forever".

@thomasrockhu-codecov
Copy link
Contributor

@sbidoul can you try using v3 or v4? The v1 version has been deprecated for some time.

@thomasrockhu-codecov thomasrockhu-codecov self-assigned this Apr 30, 2024
@codecov-hooky codecov-hooky bot added the Bug For issues and unexpected behaviors label Apr 30, 2024
@sbidoul
Copy link
Author

sbidoul commented Apr 30, 2024

@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 sbidoul changed the title GitHub Codecov action freezes jobs when uploading report GitHub Codecov v1 action freezes jobs when uploading report Apr 30, 2024
@thomasrockhu-codecov
Copy link
Contributor

@sbidoul yeah I understand that. v1 SHOULD work still, but I know those endpoints haven't been used in ages. I'm going to close this out for now, but let me know if you struggle with migrating to v4.

@sbidoul
Copy link
Author

sbidoul commented May 2, 2024

@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.

@thomasrockhu-codecov
Copy link
Contributor

@sbidoul hmm, I just ran v1 on a branch to see and it didn't block out. Is this happening all the time or just sometimes?

To just manage expectations, if this is a problem specific to action/v1 we will not be patching it, but I want to make sure that this is a problem with upload/v4 endpoint first.

@thomasrockhu-codecov
Copy link
Contributor

@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.

@sbidoul
Copy link
Author

sbidoul commented May 3, 2024

@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.

I just ran v1 on a branch to see and it didn't block out. Is this happening all the time or just sometimes?

Hard to tell for sure, but it is very prevalent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For issues and unexpected behaviors
Projects
Status: Waiting for: Product Owner
Development

Successfully merging a pull request may close this issue.

2 participants