Skip to content
callcount

kubevirt.io/kubevirt/tests/libnet.PingFromVMConsole

third-party

The 7272nd most-called third-party function by production calls. Called 82 times across 2 modules; 82 of those run outside tests and generated code.

All of kubevirt.io/kubevirt/tests/libnet → Docs on pkg.go.dev ↗

prod calls
82
non-test, non-generated
all calls
82
total callsites
modules
2
distinct callers
in loop
7%
of prod calls
in tests
0%
0 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 PingFromVMConsole from notable Go projects. Open one on the map to see what else it hammers.

where it's called

Callsites in the wild

12 representative callsites of 82, prioritizing in-loop and non-test usage. We link to source, never display it.

PingFromVMConsole · 12 of 82 callsites

top callers

The modules that reach for it

The modules that call PingFromVMConsole most in this snapshot.

  • github.com/kubevirt/kubevirt4150%
  • kubevirt.io/kubevirt4150%

siblings

More from kubevirt.io/kubevirt/tests/libnet

The other most-called functions in this package. See all →