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

tests: in_kubernetes_events: try/wait for output to make tests less flakey, re #9570. #9877

Merged
merged 1 commit into from
Jan 29, 2025

Conversation

pwhelan
Copy link
Contributor

@pwhelan pwhelan commented Jan 27, 2025

Summary

use multiple tries and wait for output in in_kubernetes_events tests, similar to the in_simple_systems and out_http tests.


Enter [N/A] in the box, if an item is not applicable to your change.

Testing
Before we can approve your change; please submit the following in a comment:

  • Example configuration file for the change
  • Debug log output from testing the change
  • Attached Valgrind output that shows no leaks or memory corruption was found

If this is a change to packaging of containers or native binaries then please confirm it works for all targets.

  • Run local packaging test showing all targets (including any new ones) build.
  • Set ok-package-test label to test for all targets (requires maintainer to do).

Documentation

  • Documentation required for this feature

Backporting

  • Backport to latest stable release.

Fluent Bit is licensed under Apache 2.0, by submitting this pull request I understand that this code will be released under the terms of that license.

…lakey. re #9570.

Signed-off-by: Phillip Adair Stewart Whelan <phillip.whelan@chronosphere.io>
@pwhelan pwhelan mentioned this pull request Jan 27, 2025
3 tasks
@edsiper edsiper merged commit 9885705 into master Jan 29, 2025
51 of 52 checks passed
@edsiper edsiper deleted the pwhelan-fix-test-rt-in_kubernetes_events-flake branch January 29, 2025 18:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants