Skip to content

Conversation

@mashhurs
Copy link
Contributor

Release notes

[rn:skip]

What does this PR do?

Sets 120m timeout to exhaustive pipeline.

Why is it important/What is the impact to the user?

No user impact

Checklist

  • [ ] My code follows the style guidelines of this project
  • [ ] I have commented my code, particularly in hard-to-understand areas
  • [ ] I have made corresponding changes to the documentation
  • [ ] I have made corresponding change to the default configuration files (and/or docker env variables)
  • [ ] I have added tests that prove my fix is effective or that my feature works

@github-actions
Copy link
Contributor

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@mashhurs mashhurs linked an issue Oct 24, 2025 that may be closed by this pull request
@mashhurs mashhurs self-assigned this Oct 24, 2025
@mergify
Copy link
Contributor

mergify bot commented Oct 24, 2025

This pull request does not have a backport label. Could you fix it @mashhurs? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
  • If no backport is necessary, please add the backport-skip label

@mashhurs mashhurs added the backport-skip Skip automated backport with mergify label Oct 24, 2025
@mashhurs mashhurs force-pushed the set-timeout-to-exhaustive-pipeline branch from 5b0748f to f5f6995 Compare October 24, 2025 23:11
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

cc @mashhurs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-skip Skip automated backport with mergify

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Set timeout to the exhaustive CI

2 participants