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

Set timeout to 6 hours on branches starting on 7.3.x #10198

Merged
merged 1 commit into from Jan 19, 2024

Conversation

sriman-confluent
Copy link
Member

@sriman-confluent sriman-confluent commented Jan 19, 2024

Description

Bumping timeout to 6 hours from the current limit of 5 hours due to builds hitting timeout. Last 2 builds on 7.3.x timed out, the last green build took 4.5 hours on Jan 3rd and the previous build directly before the green build on Jan 3rd timed out.

Noticed the branches before 7.3.x have timeout of 4 hours while branches starting on 7.3.x and after have timeout of 5 hours so just bumping the branches 7.3.x to master (will pint merge) from 5 hours to 6 hours.

Testing done

N/A

Reviewer checklist

  • Ensure docs are updated if necessary. (eg. if a user visible feature is being added or changed).
  • Ensure relevant issues are linked (description should include text like "Fixes #")
  • Do these changes have compatibility implications for rollback? If so, ensure that the ksql command version is bumped.

@sriman-confluent sriman-confluent requested a review from a team as a code owner January 19, 2024 12:33
Copy link
Member

@cadonna cadonna left a comment

Choose a reason for hiding this comment

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

Thanks @sriman-confluent !

LGTM!

@sriman-confluent sriman-confluent merged commit f4d3ece into 7.3.x Jan 19, 2024
4 of 6 checks passed
@sriman-confluent sriman-confluent deleted the 6-hour-timeout branch January 19, 2024 12:40
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.

None yet

2 participants