GetCurrentMessageLoopThreadId documentation says:

//  Returns [...] "0" if [a message loop] is not running. The latter indicates a mistake, 
// as this function should only be called after a call to one of the _OnQuit functions.

The _OnQuit functions create the message loop in a go routine (see

We hit that race in gvisor-tap-vsock with test failures when running in a gh actions runner: containers/gvisor-tap-vsock#433