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

Skip flaky test TestRateLimiter #42120

Merged
merged 1 commit into from
Dec 19, 2024

Conversation

belimawr
Copy link
Contributor

Proposed commit message

This test is flaky, see: #42059

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
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Disruptive User Impact

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

@belimawr belimawr requested a review from a team as a code owner December 19, 2024 13:43
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Dec 19, 2024
@botelastic
Copy link

botelastic bot commented Dec 19, 2024

This pull request doesn't have a Team:<team> label.

@belimawr belimawr force-pushed the flaky-test-TestRateLimiter branch from 79d2f44 to 336bf6d Compare December 19, 2024 13:44
Copy link
Contributor

mergify bot commented Dec 19, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @belimawr? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

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

Copy link
Contributor

mergify bot commented Dec 19, 2024

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

@mergify mergify bot added the backport-8.x Automated backport to the 8.x branch with mergify label Dec 19, 2024
@jlind23 jlind23 merged commit df4832e into elastic:main Dec 19, 2024
9 of 21 checks passed
@jlind23
Copy link
Collaborator

jlind23 commented Dec 19, 2024

force merging this to get main back to a stable state.

mergify bot pushed a commit that referenced this pull request Dec 19, 2024
This test is flaky, see: #42059

(cherry picked from commit df4832e)
andrewkroh pushed a commit that referenced this pull request Dec 19, 2024
This test is flaky, see: #42059

(cherry picked from commit df4832e)

Co-authored-by: Tiago Queiroz <tiago.queiroz@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-8.x Automated backport to the 8.x branch with mergify needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants