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
.github: Disable flow validation in flaky tests #16388
Conversation
The flow validation of cilium connectivity test has been reported to be flaky in several of the ci-xxx tests [1, 2, 3]. To reduce CI noise, we can disable flow validation until the flakes are fixed. 1 - cilium#16292. 2 - cilium#16291. 3 - cilium#16096. Signed-off-by: Paul Chaignon <paul@cilium.io>
I updated the branch to also disable in the Kind1.19 test given it's also failing there (cf. #16392). |
e798d6c
to
a5b54a7
Compare
EDIT: That's just because these tests execute the master versions on PR 🤦 |
Al team reviews are covered. The Kind1.19 test is passing. Other triggered tests are running the master version, not this PR version. Marking as ready to merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pchaigno can you validate that the client-to-client-client-ingress-from-client
test in the aks conformance tests has nothing to do with this PR? Otherwise LGTM.
NVM, didn't see the previous comment
Seems like we missed that in cilium#16388. Fixes 49ce8e9 Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
Seems like we missed that in cilium#16388. Fixes 49ce8e9 Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
In #16388, we disabled flow validation as it was unstable in the CLI. In #16617, we partially moved to `warning` for testing purposes. This reverts back to `disabled` for all connectivity tests in order to be consistent. Also fix missing disabled flow validation in EKS, as it seems like we missed that one in #16388. We can always enable flow validation again later once we are confident flow validation works better in the CLI. Fixes 49ce8e9 Fixes 21c9b41 Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
In #16388, we disabled flow validation as it was unstable in the CLI. In #16617, we partially moved to `warning` for testing purposes. This reverts back to `disabled` for all connectivity tests in order to be consistent. Also fix missing disabled flow validation in EKS, as it seems like we missed that one in #16388. We can always enable flow validation again later once we are confident flow validation works better in the CLI. Fixes 49ce8e9 Fixes 21c9b41 Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
In #16388, we disabled flow validation as it was unstable in the CLI. In #16617, we partially moved to `warning` for testing purposes. This reverts back to `disabled` for all connectivity tests in order to be consistent. Also fix missing disabled flow validation in EKS, as it seems like we missed that one in #16388. We can always enable flow validation again later once we are confident flow validation works better in the CLI. Fixes 49ce8e9 Fixes 21c9b41 Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
[ upstream commit 36aa4f7 ] In #16388, we disabled flow validation as it was unstable in the CLI. In #16617, we partially moved to `warning` for testing purposes. This reverts back to `disabled` for all connectivity tests in order to be consistent. Also fix missing disabled flow validation in EKS, as it seems like we missed that one in #16388. We can always enable flow validation again later once we are confident flow validation works better in the CLI. Fixes 49ce8e9 Fixes 21c9b41 Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com> Signed-off-by: André Martins <andre@cilium.io>
[ upstream commit 36aa4f7 ] In #16388, we disabled flow validation as it was unstable in the CLI. In #16617, we partially moved to `warning` for testing purposes. This reverts back to `disabled` for all connectivity tests in order to be consistent. Also fix missing disabled flow validation in EKS, as it seems like we missed that one in #16388. We can always enable flow validation again later once we are confident flow validation works better in the CLI. Fixes 49ce8e9 Fixes 21c9b41 Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com> Signed-off-by: André Martins <andre@cilium.io>
The flow validation of cilium connectivity test has been reported to be flaky in several of the
ci-xxx
tests [1, 2, 3, 4]. To reduce CI noise, we can disable flow validation until the flakes are fixed.1 - #16292.
2 - #16291.
3 - #16096.
4 - #16392.