kubevirt.io/kubevirt/tests/framework/matcher.BeReady
third-partyThe 4759th most-called third-party function by production calls. Called 139 times across 2 modules; 124 of those run outside tests and generated code.
All of kubevirt.io/kubevirt/tests/framework/matcher → Docs on pkg.go.dev ↗
- prod calls
- 124
- non-test, non-generated
- all calls
- 139
- total callsites
- modules
- 2
- distinct callers
- in loop
- 0%
- of prod calls
- in tests
- 11%
- 15 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 function61%A direct call to an exported package function, resolved by type.
- Package function (by syntax)39%A package function in a module outside the crawl, keyed by import path.
who calls this
Notable callers
Production calls into BeReady from notable Go projects. Open one on the map to see what else it hammers.
- KubeVirt 53 43%
where it's called
Callsites in the wild
12 representative callsites of 139, prioritizing in-loop and non-test usage. We link to source, never display it.
-
-
kubevirt.io/kubevirt @v1.9.0
tests/compute/vm_lifecycle.go:56
-
-
kubevirt.io/kubevirt @v1.9.0
tests/libvmops/lifecycle.go:57
-
-
kubevirt.io/kubevirt @v1.9.0
tests/instancetype/instancetype.go:57
-
-
kubevirt.io/kubevirt @v1.9.0
tests/compute/subresources/start.go:60
-
-
kubevirt.io/kubevirt @v1.9.0
tests/instancetype/memory_overcommit.go:61
-
kubevirt.io/kubevirt @v1.9.0
tests/compute/subresources/stop.go:62
-
top callers
The modules that reach for it
The modules that call BeReady most in this snapshot.
- kubevirt.io/kubevirt8561%
- github.com/kubevirt/kubevirt5439%
siblings
More from kubevirt.io/kubevirt/tests/framework/matcher
The other most-called functions in this package. See all →