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

[8.x](backport #41358) x-pack/filebeat/input/{cel,httpjson}: fix flaky test #41406

Merged
merged 1 commit into from
Oct 24, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Oct 23, 2024

Proposed commit message

Do not use uncontrolled randomisation in tests where it is not necessary. The retry tests in the httpjson and cel packages were using a randomised 5xx HTTP status code to trigger the retry behaviour of the the go-retryablehttp package. This had the unfortunate consequence of causing 2% of test runs to fail.

The reason for this is given in the go-retryablehttp documentation[1]:

Mainly, if an error is returned by the client (connection errors, etc.), or if a 500-range response code is received (except 501), then a retry is invoked after a wait period.

Since the package is already tested, and is documented to accept all 5xx status codes except 501 to cause a retry, just use 500.

[1]https://pkg.go.dev/github.com/hashicorp/[email protected]#section-readme

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


This is an automatic backport of pull request #41358 done by [Mergify](https://mergify.com).

Do not use uncontrolled randomisation in tests where it is not necessary. The
retry tests in the httpjson and cel packages were using a randomised 5xx HTTP
status code to trigger the retry behaviour of the the go-retryablehttp
package. This has the unfortunate consequence of causing 2% of test runs to
fail.

The reason for this is given in the go-retryablehttp documentation[1]:

	Mainly, if an error is returned by the client (connection errors,
	etc.), or if a 500-range response code is received (except 501),
	then a retry is invoked after a wait period.

Since the package is already tested, and is documented to accept all 5xx
status codes except 501 to cause a retry, just use 500.

[1]https://pkg.go.dev/github.com/hashicorp/[email protected]#section-readme

(cherry picked from commit 794b832)
@mergify mergify bot requested a review from a team as a code owner October 23, 2024 19:33
@mergify mergify bot added the backport label Oct 23, 2024
@mergify mergify bot assigned efd6 Oct 23, 2024
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Oct 23, 2024
@botelastic
Copy link

botelastic bot commented Oct 23, 2024

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

@efd6 efd6 merged commit efd7de1 into 8.x Oct 24, 2024
20 of 22 checks passed
@efd6 efd6 deleted the mergify/bp/8.x/pr-41358 branch October 24, 2024 01:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant