-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
test: Wait for cilium monitor to match expected output #15848
Conversation
In some tests we check the output of cilium monitor and compare it against expected substrings (e.g., allowed verdict). When doing so, we however need to repeat with a timeout until it matches as the cilium monitor output may be buffered and may not match the expected output as soon as we check. This commit fixes a couple cases where we forgot to wait for the output to match. It is expected to fix flake cilium#14676. Signed-off-by: Paul Chaignon <paul@cilium.io>
d6ffc42
to
cc10799
Compare
Only Runtime is required since only Runtime tests are touched. test-runtime |
Do we need to backport this to v1.9? I believe I have just observed the issue in v1.9 backports PR #16910: |
It's hard to tell for sure because we're missing the artifacts. I've marked #16759, #16540, and #16489 for backports to ensure we have artifacts in the future.
I'm not against backporting this PR as well 👍 |
In some tests we check the output of
cilium monitor
and compare it against expected substrings (e.g., allowed verdict). When doing so, we however need to repeat with a timeout until it matches as thecilium monitor
output may be buffered and may not match the expected output as soon as we check. This pull request fixes a couple cases where we forgot to wait for the output to match.It is expected to fix flake #14676. See details at #14676 (comment)