Closed
Description
There still seems to a test flake in some of the connection tests (conn_test.go) - examples of flake:
TestConn/AcceptTestConn/PeerConcurrentTestConn/NetConn
The relevant part of this log seems to be:
t.go:56: 2022-02-01 18:04:44.677 [DEBUG] (server) <conn.go:226> selected candidate pair changed {"local": {"foundation": "608990844", "priority": 2130706431, "address": "1.2.3.5", "protocol": 1, "port": 5318, "type": 1, "component": 1, "relatedAddress": "", "relatedPort": 0, "tcpType": ""}, "remote": {"foundation": "422338508", "priority": 2130706431, "address": "1.2.3.4", "protocol": 1, "port": 5081, "type": 1, "component": 1, "relatedAddress": "", "relatedPort": 0, "tcpType": ""}}
t.go:56: 2022-02-01 18:04:44.677 [DEBUG] (server) <conn.go:222> dtls transport state updated {"state": "connecting"}
t.go:56: 2022-02-01 18:04:44.679 [DEBUG] (server) <conn.go:148> ice connection state updated {"state": "connected"}
t.go:56: 2022-02-01 18:04:44.680 [DEBUG] (client) <conn.go:148> ice connection state updated {"state": "connected"}
t.go:56: 2022-02-01 18:04:44.680 [DEBUG] (client) <conn.go:148> ice connection state updated {"state": "checking"}
t.go:56: 2022-02-01 18:04:44.680 [DEBUG] (client) <conn.go:226> selected candidate pair changed {"local": {"foundation": "422338508", "priority": 2130706431, "address": "1.2.3.4", "protocol": 1, "port": 5081, "type": 1, "component": 1, "relatedAddress": "", "relatedPort": 0, "tcpType": ""}, "remote": {"foundation": "3674517152", "priority": 1862270975, "address": "1.2.3.5", "protocol": 1, "port": 5318, "type": 3, "component": 1, "relatedAddress": "", "relatedPort": 0, "tcpType": ""}}
t.go:56: 2022-02-01 18:04:44.673 [DEBUG] (server) <conn.go:236> sending local candidate {"candidate": "candidate:608990844 1 udp 2130706431 1.2.3.5 5318 typ host"}
t.go:56: 2022-02-01 18:04:44.681 [DEBUG] (client) <conn.go:350> accepting candidate {"candidate": "candidate:608990844 1 udp 2130706431 1.2.3.5 5318 typ host"}
t.go:56: 2022-02-01 18:05:14.680 [DEBUG] (server) <conn.go:222> dtls transport state updated {"state": "failed"}
t.go:56: 2022-02-01 18:05:14.681 [DEBUG] (server) <conn.go:186> rtc connection updated {"state": "failed"}
t.go:56: 2022-02-01 18:05:14.681 [DEBUG] (server) <channel.go:268> datachannel closing with error {"id": 2, "label": "echo"} ...
where the candidate pair has been updated, but the dtls transport state fails, for some reason.