Investigate the TestLockingUpWithAThrow failures

[olegbespalov]

What?

In #54, along with introducing the tests on the Windows platform, we found that the TestLockingUpWithAThrow was causing issues. After a quick investigation, we localized that the issue was caused by the high number of connections that this test tried to create and change, as 9dee277 could help. It seems like these issues for windows starts with ~250 connections there.

On the other side, it raises the question that maybe it's a real issue, and we hit the behavior when we get the lock somewhere, thinking:

If the number of connections in the test is 1000, and we try to run:

go test -timeout 2m -count=150 -run ^TestLockingUpWithAThrow$ github.com/grafana/xk6-websockets/websockets

Even on Linux, we could reach timeout 😢

So we should investigate and either fix or at least understand the root cause of the issue.

Why?

It's important to know what the limits are or if there is a bug exists.