Files
nats-server/server
Phil Pennock 7aacba4bda tests: don't allocate fixed ports from random range
When a socket is bound for IP stack protocols with port == 0, the kernel picks
a free port in a specific range and binds it; on Linux, the range can be seen
(and modified) with `sysctl net.ipv4.ip_local_port_range` or looking in
`/proc/sys/net/ipv4/ip_local_port_range`.  This defaults to 32768:60999.

When binding explicit ports (for tests), don't use a port number from that
range, or there will be flaky tests as periodically that port will already be
in use from another test.

This renumbers all the JS clustering tests I found binding in that range to be
beneath that range; I checked the code to ensure the new port wasn't already in
use.
2021-10-27 13:46:43 -04:00
..
2020-05-19 14:15:11 -07:00
2021-07-22 11:27:34 -04:00
2021-04-09 15:18:06 -07:00
2021-10-27 09:20:31 -07:00
2021-10-25 13:12:37 -07:00
2021-08-26 16:52:43 +02:00
2021-08-26 16:52:43 +02:00
2020-02-25 19:53:09 -05:00
2021-05-26 08:04:50 +02:00
2021-10-14 09:25:21 -07:00
2021-07-23 10:19:07 +01:00
2021-10-25 13:12:37 -07:00
2021-10-26 20:09:00 -07:00
2021-01-14 01:14:52 -08:00
2021-01-14 01:14:52 -08:00
2021-09-21 08:02:11 -07:00
2021-10-11 23:19:56 +08:00
2021-10-26 20:09:00 -07:00
2021-10-18 17:53:56 -07:00
2020-06-12 10:03:47 -06:00
2019-11-14 20:05:32 -07:00
2021-09-01 14:55:26 -07:00
2021-04-12 10:17:13 -07:00
2019-12-12 11:58:24 -07:00
2021-10-26 20:09:00 -07:00
2021-10-26 20:09:00 -07:00
2021-09-13 15:22:05 +03:00
2021-10-12 11:17:58 -06:00