test: Quarantine test with secondary NodePort device #15003
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
The "from outside of cluster" section of that test is flaky (cf. cilium#12511). We can therefore quarantine the test when it's running with the third node. Related: cilium#12511 Signed-off-by: Paul Chaignon <paul@cilium.io>
pchaigno
added
area/CI
nebril
approved these changes
Feb 17, 2021
|
Cluster scaling failed. |
|
Unfortunately, it won't completely eliminate flakes. Other NodePort BPF tests when requests are sent from outside flake too. |
@brb They do flake sometimes, but clearly not as often: compare this dashboard for secondary device test to that one for all NodePort BPF tests (>10% vs. <1% failures on master). |
|
OT: got it reproduced on local machines, but I don't have a clue yet why it the first request fails. |
pchaigno
added
the
ready-to-merge
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.
The "from outside of cluster" section of that test is flaky (cf. #12511). We can therefore quarantine the test when it's running with the third node.
Related: #12511