Oran Agra e258a1c087 tests: each test client work on a distinct port range ... apparently when running tests in parallel (the default of --clients 16), there's a chance for two tests to use the same port. specifically, one test might shutdown a master and still have the replica up, and then another test will re-use the port number of master for another master, and then that replica will connect to the master of the other test. this can cause a master to count too many full syncs and fail a test if we run the tests with --single integration/psync2 --loop --stop see Probmem 2 in #7314		2020-05-26 11:17:08 +03:00
..
assets	Fix test "server is up" detection after logging changes.	2016-12-19 16:49:58 +01:00
cluster	Add a test to prove current tcl cluster client can not handle keys with hash tag.	2020-05-11 13:14:18 +08:00
helpers	revert an accidental test code change done as part of the tls project	2019-12-01 16:10:09 +02:00
integration	Disconnect chained replicas when the replica performs PSYNC with the master always to avoid replication offset mismatch between master and chained replicas.	2020-05-21 18:42:10 -07:00
modules	Fix memory corruption in moduleHandleBlockedClients	2020-04-01 12:53:26 +03:00
sentinel	TLS: Configuration options.	2019-10-07 21:07:27 +03:00
support	tests: each test client work on a distinct port range	2020-05-26 11:17:08 +03:00
tmp	minor fixes to the new test suite, html doc updated	2010-05-14 18:48:33 +02:00
unit	tests: each test client work on a distinct port range	2020-05-26 11:17:08 +03:00
instances.tcl	tests: each test client work on a distinct port range	2020-05-26 11:17:08 +03:00
test_helper.tcl	tests: each test client work on a distinct port range	2020-05-26 11:17:08 +03:00