stackage-server: "Basically every test that tries to connect to localhost/127.0.0.1 fails"

[chreekat]

Issue reported by the curators today.

[chreekat]

A test that is expected to pass fails as seen below.

The error string "Cannot assign requested address" may indicate resource exhaustion.

             test/Servant/Auth/ClientSpec.hs:66:7:
             1) Servant.Auth.Client, The JWT combinator, HasClient, succeeds when the token does not have expiry
                  Falsifiable (after 1 test):
                    User {name = "", _id = ""}
                  expected: Right 0
                   but got: Left (ConnectionError (HttpExceptionRequest Request {
                              host                 = "localhost"
                              port                 = 35219
                              secure               = False
                              requestHeaders       = [("Accept","application/json;charset=utf-8,application/json"),("Authorization","<REDACTED>")]
                              path                 = ""
                              queryString          = ""
                              method               = "GET"
                              proxy                = Nothing
                              rawBody              = False
                              redirectCount        = 10
                              responseTimeout      = ResponseTimeoutDefault
                              requestVersion       = HTTP/1.1
                              proxySecureMode      = ProxySecureWithConnect
                            }
                             (ConnectionFailure Network.Socket.connect: <socket: 6>: unsupported operation (Cannot assign requested address))))

[chreekat]

Most examples of the error (from ~curators/stackage/automated/lts-build.log) have a port number that is duplicated across 2-3 error messages. E.g. the very next example of the error after the one listed above also has host="localhost" and port = 35219. Maybe the tests were stepping on each other's toes?

[alaendle]

Lets see if we got new insights from feedback in yesodweb/wai#1019, but nonetheless this has nothing to do with our infrastructure; so I suggest to just close this issue.

[chreekat]

Ok! Just reopen it if that other issue isn't the whole story.