Socket test can fail if hard-coded port is unavailable

Description

I was unable to run the Clojure tests due to this problem. There is a test that hardcodes a port and something else on my machine happened to be using that port.

The patch avoids binding a hard-coded port in the test.

Patch: socket-test.patch

Screened by:

Environment

None

Attachments

1

Activity

Show:

Alex Miller February 26, 2015 at 5:57 PM

No good reason not to fix it! Silly test.

Andy Fingerhut February 26, 2015 at 5:31 PM

I used to try running the prescreen tests in parallel for two different JDKs on the same machine, and I probably stopped doing that because of this. My use case is a very unusual one, and not a good reason to change this by itself, but my use case certainly made this conflict happen regularly.

Completed

Details

Assignee

Reporter

Labels

Approval

Patch

Priority

Affects versions

Fix versions

Created February 26, 2015 at 4:36 PM
Updated March 27, 2015 at 8:12 PM
Resolved March 27, 2015 at 8:12 PM