kubevirt.io/kubevirt/tests/libwait.WaitForSuccessfulVMIStart
third-partyThe 3178th most-called third-party function by production calls. Called 322 times across 2 modules; 186 of those run outside tests and generated code.
All of kubevirt.io/kubevirt/tests/libwait → Docs on pkg.go.dev ↗
- prod calls
- 186
- non-test, non-generated
- all calls
- 322
- total callsites
- modules
- 2
- distinct callers
- in loop
- 4%
- of prod calls
- in tests
- 42%
- 136 calls
- resolved
- 100%
- to a known target
resolution mix
How each call resolves
How each call was attributed. Only resolved kinds, where the target function is known, count toward the ranking. Interface dispatch and unresolved receivers are reported separately and never guessed. Read the taxonomy →
- Package function50%A direct call to an exported package function, resolved by type.
- Package function (by syntax)50%A package function in a module outside the crawl, keyed by import path.
who calls this
Notable callers
Production calls into WaitForSuccessfulVMIStart from notable Go projects. Open one on the map to see what else it hammers.
- KubeVirt 93 50%
where it's called
Callsites in the wild
12 representative callsites of 322, prioritizing in-loop and non-test usage. We link to source, never display it.
- in loop
-
kubevirt.io/kubevirt @v1.9.0
tests/migration/priority.go:88
in loop - in loop
-
kubevirt.io/kubevirt @v1.9.0
tests/storage/datavolume.go:337
in loop - in loop
-
kubevirt.io/kubevirt @v1.9.0
tests/migration/eviction_strategy.go:463
in loop - in loop
-
kubevirt.io/kubevirt @v1.9.0
tests/operator/operator.go:2988
in loop - in loop test
-
kubevirt.io/kubevirt @v1.9.0
tests/hyperv_test.go:166
in loop test -
-
kubevirt.io/kubevirt @v1.9.0
tests/performance/realtime.go:42
top callers
The modules that reach for it
The modules that call WaitForSuccessfulVMIStart most in this snapshot.
- github.com/kubevirt/kubevirt16150%
- kubevirt.io/kubevirt16150%
siblings
More from kubevirt.io/kubevirt/tests/libwait
The other most-called functions in this package. See all →