ci: disable failing test on net-next (#18520)#18544
Merged
kkourt merged 1 commit intocilium:masterfrom Jan 20, 2022
Merged
Conversation
`K8sPolicyTest Multi-node policy test validates fromEntities policies Validates fromEntities all policy` has been failing consistently on net-next testing pipelines after we upgraded the net-next Vagrant VM in 8bf4e22. We disable the test until it is fixed (tracked in cilium#18520). Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
Member
Author
|
/test-1.23-net-next |
twpayne
approved these changes
Jan 19, 2022
Member
Author
|
net-next passed, this change does not need any other CI testing, marking as ready to merge. |
6 tasks
6 tasks
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
K8sPolicyTest Multi-node policy test validates fromEntities policies Validates fromEntities all policyhas been failing consistently on net-next testing pipelines after we upgraded the net-next Vagrant VM in 8bf4e22.We disable the test until it is fixed (tracked in #18520).