Closed viktor-kurchenko closed 4 days ago
kind failure might be legitimate. i see a similar set of tests failing consistently 💭
❌ 1/13 tests failed (0/85 actions), 5 tests skipped, 0 scenarios skipped:
Test [dns-only]:
📋 Test Report [test-namespace-2]
❌ 1/11 tests failed (0/133 actions), 5 tests skipped, 0 scenarios skipped:
Test [client-egress-l7-tls-deny-without-headers]:
📋 Test Report [test-namespace-3]
❌ 1/12 tests failed (0/83 actions), 4 tests skipped, 0 scenarios skipped:
Test [client-egress-l7-tls-headers]:
📋 Test Report [test-namespace-4]
❌ 1/11 tests failed (0/93 actions), 4 tests skipped, 0 scenarios skipped:
Test [client-egress-l7-set-header]:
kind failure might be legitimate. i see a similar set of tests failing consistently 💭
Oh, no... I'll take a look! Thanks!
@michi-covalent it should work now.
let me rebase to pick up the multicluster fix
The fix for connectivity tests ExternalTargetCANamespace name. The name must be namespace specific in case of tests concurrent run for proper CiliumNetworkPolicy provisioning.
test-concurrency=5
)test-concurrency=5
)test-concurrency
param)Fix: https://github.com/cilium/cilium-cli/issues/2644