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] Use if: !cancelled() instead of if: always() #1266

Merged
merged 1 commit into from
Jan 27, 2025

Conversation

rfc2822
Copy link
Member

@rfc2822 rfc2822 commented Jan 27, 2025

Currently tests (like instrumented tests) are not cancellable. This is especially annoying when there's a problem test causes tests to run indefinitely, like here. I think it will time out somewhen but until then it blocks one of our runners.

Seems to be caused by recent Github changes: https://github.com/orgs/community/discussions/26303

To make test jobs cancellable, see https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/evaluate-expressions-in-workflows-and-actions#always

I have cancelled the Instrumented tests job to test it, and it worked.

CC @euuurgh because it's CI

@rfc2822 rfc2822 added the bug Something isn't working label Jan 27, 2025
@rfc2822 rfc2822 marked this pull request as ready for review January 27, 2025 11:32
@rfc2822 rfc2822 self-assigned this Jan 27, 2025
@rfc2822 rfc2822 requested a review from sunkup January 27, 2025 11:33
@rfc2822 rfc2822 merged commit 50cbac1 into main-ose Jan 27, 2025
12 checks passed
@rfc2822 rfc2822 deleted the ci-dont-use-if-always branch January 27, 2025 12:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants