Olivia
Olivia copied to clipboard
Resolve consistent build failures due to listen port
Right now whenever unit tests are ran, there's a high likelihood of at least one of the (6 total) tests failing, due to a port already being listened on. This is pretty agitating, having to continually run the tests, so I need to figure out a better way of running tests/choosing a port.
Randomized ports are one thing, but I either have to rely on the travis CI config or check, at boot time, if we're in a test environment--this still relies on travis.