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
ci: quarantine K8sAgentIstioTest
#24476
Conversation
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.
CI is failing on legit failure. Seems like a matter of defining an inline func () { ... }
This test has been consistently failing since March 10 on Kernel 4.19 pipelines for K8s 1.17 - 1.24. Since we are considering deprecating the Istio integration (cilium#24204), we quarantine the test as it's unclear if we should invest in understanding the issue and fixing it. Signed-off-by: Nicolas Busseneau <nicolas@isovalent.com>
b211c0c
to
64ef7f1
Compare
🤦🏻♂️ Yes, correct. Not sure why it wasn't picked up by my local environment, it seems like I broke something and now nothing gets analysed. |
/test |
/test-missed-k8s Job 'Cilium-PR-K8s-1.24-kernel-4.19' failed: Click to show.Test Name
Failure Output
If it is a flake and a GitHub issue doesn't already exist to track it, comment |
Various flakes / Vagrant provisioning issue were hit, but it's fine, I only wanted to check if Istio tests were indeed quarantined from the intended jobs, and they are. Marking ready to merge. |
This test has been consistently failing since March 10 on Kernel 4.19 pipelines for K8s 1.17 - 1.24.
Since we are considering deprecating the Istio integration (#24204), we quarantine the test as it's unclear if we should invest in understanding the issue and fixing it.