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

CI: add retry for steps/jobs on timeout. #1554

Closed
NobodyXu opened this issue Jan 5, 2024 · 5 comments · Fixed by #1561 or #1591
Closed

CI: add retry for steps/jobs on timeout. #1554

NobodyXu opened this issue Jan 5, 2024 · 5 comments · Fixed by #1561 or #1591
Labels
Blocked: upstream Fix or feature is needed to be implemented upstream (in a dependency)

Comments

@NobodyXu
Copy link
Member

NobodyXu commented Jan 5, 2024

          I think we might need to add retry for our actions on timeout.

Originally posted by @NobodyXu in #1553 (comment)

@NobodyXu
Copy link
Member Author

NobodyXu commented Jan 5, 2024

Context: #1553 failed multiple times due to timeout in CI.

@NobodyXu
Copy link
Member Author

NobodyXu commented Jan 6, 2024

For action download-artifacts, it is a known upstream issue:

actions/download-artifact#249

@NobodyXu
Copy link
Member Author

NobodyXu commented Jan 6, 2024

Opened #1560 for cargo-binstall related CI supurious failure

@NobodyXu NobodyXu added the Blocked: upstream Fix or feature is needed to be implemented upstream (in a dependency) label Jan 6, 2024
@passcod
Copy link
Member

passcod commented Jan 7, 2024

We could downgrade to v3 for artifact

@NobodyXu
Copy link
Member Author

NobodyXu commented Jan 7, 2024

Yeah, that's reasonable, I will do it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blocked: upstream Fix or feature is needed to be implemented upstream (in a dependency)
Projects
None yet
2 participants