[BUG] The test TestConnectToSocket times out very rarely

[MaelyssGilliard]

Description (Actual behavior)

The test TestConnectToSocket times out very rarely (we don't have a specific failure rate) in the CI. It is probably the same problem than in issue #709 that wasn't completely fixed but only has a drastically reduced rate after the proposed solution.

Expected behavior

The test is not supposed to fail. The logs of the test are supposed to look like this:

How to reproduce

We don't know how to reproduce the bug, it happened only on the CI

Version & Environment

This bug was reproduced on:

• Commit: 8b1cda8e7542eb68b8c9a0b83f41d12f0846dd54

Front-ends:

• [ ] Fe1-Web (please include browser's names & version)
• [ ] Fe2-Android (please specify if phone or emulation, and Android version)
• [x] Not applicable

Back-ends:

• [x] Be1-Go
• [ ] Be2-Scala
• [ ] Not applicable

Workaround

Re-run all jobs when the CI fails.

Possible root cause

The problem comes probably from a concurrency error, where only the read pump or the write pump closes when a socket is closed while a message is being sent or received through the socket.