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] Sets a 20 min timeout for clang-tidy #245

Merged
merged 1 commit into from
Jul 26, 2022
Merged

Conversation

CarlosNihelton
Copy link
Collaborator

@CarlosNihelton CarlosNihelton commented Jul 25, 2022

GitHub history shows that succesful runs finish under 15 minutes long. Longer runs required manual cancellation.
Not sure the cause, but let's limit the runs to 20 minutes for now to avoid depending on manual cancellations, at least.
GitHub default limit seems too much: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idtimeout-minutes

GitHub history shows that runs over 15 minutes long ended up cancelled.
Cancelling is manual.
Not sure the cause, but let's limit the runs to 20 minutes for now.
This avoids depending on manual cancellations.
@CarlosNihelton CarlosNihelton changed the title Sets a 20 min timeout for clang-tidy [CI] Sets a 20 min timeout for clang-tidy Jul 25, 2022
@CarlosNihelton CarlosNihelton marked this pull request as ready for review July 25, 2022 16:02
Copy link
Collaborator

@EduardGomezEscandell EduardGomezEscandell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

The longest I found in the last week or so is this one which took 12 minutes. 20 is a good, safe choice but if we felt it necessary we could probably go down to 15 in the future.

@CarlosNihelton CarlosNihelton merged commit 3b5aa7a into main Jul 26, 2022
@CarlosNihelton CarlosNihelton deleted the qa-timeout-ci branch July 26, 2022 09:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants