You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Chances are that this could also time out if you're lucky and run it on your local workstation with go test -race but I've only seen this crop up on CI runs and not on my machine (yet).
In this case, it seems like a call to Libvirt.Disconnect is never returning. The goroutines labeled "semacquire" are kind of interesting but they don't have an indicator that suggests how long they've been in that state.
It appears the use of a channel close as a barrier creates the race condition as the connection could go down and be re-established without a Disconnect completing. A sync.Mutex for graceful shutdown may need to be in place to guard against a Connect/Dial to an actively disconnecting instance.
This design appears to existing in socket as well.
Chances are that this could also time out if you're lucky and run it on your local workstation with
go test -race
but I've only seen this crop up on CI runs and not on my machine (yet).In this case, it seems like a call to Libvirt.Disconnect is never returning. The goroutines labeled "semacquire" are kind of interesting but they don't have an indicator that suggests how long they've been in that state.
stack trace
The text was updated successfully, but these errors were encountered: