Module state 

Shared container state: lock files, per-process resource registry, and stale-process pruning.

Test binaries from several processes may share one reusable container. The state file records which process created which resources (for example per-test databases), so a later run can clean up resources whose owner process already exited. During nextest runs, dead process entries remain associated with the current run until a later run can reclaim them without interleaving destructive cleanup with active schema provisioning.

Structs

ContainerLease

Lease that prunes reclaimable process entries from a service’s state file on drop.

ContainerStateLock

Exclusive filesystem lock guarding one service’s state file.

SharedContainerEndpoint

Last verified endpoint of one reusable suite container.

SharedContainerState

Serializable registry of test processes and the resources they created.