4 Commits (219e9f8297d7980739341076511f9d2b9b44a5d5)

Author	SHA1	Message	Date
James Phillips	fe36ed6412	Bumps freeport's block size. ... We were seeing some rollover artifacts where something would be shut down so a port could be re-used, but it was still being referenced by some running thing. This gives more time before rolling over.	7 years ago
Alex Dadgar	0fccef237d	Initialize freeport lazily to avoid runtime issues ... This PR makes freeport initialize lazily rather than using an init method.	7 years ago
Alex Dadgar	17dcbb1912	Make freeport testing friendly ... This PR allows the caller to decide if they would like to have the calling test fail, have the caller panic on error, or handle the errors themselves.	7 years ago
Frank Schroeder	c94751ad43	test: replace porter tool with freeport lib ... This patch removes the porter tool which hands out free ports from a given range with a library which does the same thing. The challenge for acquiring free ports in concurrent go test runs is that go packages are tested concurrently and run in separate processes. There has to be some inter-process synchronization in preventing processes allocating the same ports. freeport allocates blocks of ports from a range expected to be not in heavy use and implements a system-wide mutex by binding to the first port of that block for the lifetime of the application. Ports are then provided sequentially from that block and are tested on localhost before being returned as available.	7 years ago