gloo
gloo copied to clipboard
Barrier followed by context destruction causes some participants to fail
The shutdown code may be a bit too aggressive here. We should have a stress test for the termination scenario where we loop on (context creation, barrier, context destruction) and verify nobody raises.
May be related to write queues not draining when getting a closure signal from another pair.