|
Ran
|
Jobs
1
|
Files
151
|
Run time
1min
|
Badge
README BADGES
|
push
github
test(e2e): wait for the admission webhooks before the first spec (#149) The suite starts right after the operator is installed. The webhook Service only takes connections once the operator pod's endpoint reaches kube-proxy, a moment after the pod turns ready, so the first spec could get failed calling webhook "mvalkey-v1alpha1.kb.io": ... connect: connection refused and, the suite being ordered, skip every spec after it. On Kind with Kubernetes v1.34.11 this happened 1 s after `helm --wait` returned, 12 s after the operator's webhook server had started serving. waitForAdmission repeats a server-side dry-run create, which goes through admission without creating anything, until the webhooks answer. BeforeAll calls it when the operator was installed before the suite (SKIP_DEPLOY_OPERATOR), and the operator spec calls it after deploying one. (cherry picked from commit a8d8cdff8)
7766 of 21918 relevant lines covered (35.43%)
0.4 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 36411931026.1 | 151 |
35.43
|
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
|---|