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

fix(logs): reset eventChan everytime KarmorLogStart() is called #1798

Merged
merged 1 commit into from
Jul 11, 2024

Conversation

navin772
Copy link
Contributor

@navin772 navin772 commented Jul 8, 2024

Purpose of PR?:

Draining the eventChan in every KarmorLogStart() function call will reduce flakiness in the tests.

Does this PR introduce a breaking change?

No

If the changes in this PR are manually verified, list down the scenarios covered::

Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs

Checklist:

  • Bug fix. Fixes #
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • PR Title follows the convention of <type>(<scope>): <subject>
  • Commit has unit tests
  • Commit has integration tests

@Aryan-sharma11 Aryan-sharma11 force-pushed the reset-karmorlog-evenChan branch 2 times, most recently from b8c865f to 7ccccaa Compare July 10, 2024 08:45
This will reduce flakiness in the tests

Signed-off-by: Navin Chandra <[email protected]>
@Prateeknandle Prateeknandle merged commit 998bfda into kubearmor:main Jul 11, 2024
17 checks passed
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

3 participants