There are no guards around NetworkInterfaceMock::NetworkOperation::setResponse() here and here. This means that tests that feature timeouts or interruptions cannot safely experience an interruption during a response. Poorly written tests may also experience undefined behavior because it is not explicitly defined who wins "races".