test: Add klog lock error to allow-list #16698
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pchaigno
added
area/CI
pchaigno
force-pushed
the
ci-add-error-allow-list
branch
from
e7d3b71
to
275dd05
Compare
nbusseneau
approved these changes
Jun 30, 2021
This error message happened in CI and seems to be a less frequent variation of known klog error messages [1]. 1 - cilium#16402 (comment) Signed-off-by: Paul Chaignon <paul@cilium.io>
pchaigno
force-pushed
the
ci-add-error-allow-list
branch
from
275dd05
to
571f4b0
Compare
|
Tests are compiling, previous end-to-end test runs were okay, and review is in. Marking as ready and merging. |
pchaigno
added
the
ready-to-merge
|
@pchaigno wait, how do we know that Cilium isn't causing the apiserver connectivity issue that leads to |
|
It might. It's not a new error, but we should definitely track it and figure out the root cause. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This error message happened in CI and seems to be a less frequent variation of known klog error messages [1].
1 - #16402 (comment)