Files
nats-server/server
Ivan Kozlovic afb5086f17 [CHANGED] LeafNode: remotes from same server binding to same hub account
Previously, the server would reject a second remote leafnode connection
from the same server if it was binding to the same account on the hub
even if the remote was using different local accounts.

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
2023-06-20 18:44:52 -06:00
..
2023-02-10 10:29:26 +00:00
2023-01-27 08:35:59 -08:00
2023-05-16 14:15:22 -06:00
2023-06-05 14:13:18 -07:00
2022-09-08 11:28:23 -06:00
2023-06-13 15:48:05 -04:00
2023-06-09 09:29:13 -07:00
2023-06-10 20:56:42 -07:00
2023-06-10 20:56:42 -07:00
2023-06-19 16:30:05 -07:00
2023-06-10 15:23:33 -07:00
2022-11-14 08:28:19 -08:00
2023-04-03 09:32:28 -06:00
2023-06-10 20:56:42 -07:00
2023-06-02 13:19:22 +03:00
2023-06-10 17:03:36 -07:00
2023-05-15 15:44:38 -07:00
2023-02-10 10:29:26 +00:00
2023-02-10 10:29:26 +00:00
2023-05-15 15:44:38 -07:00
2023-06-13 17:22:21 -06:00
2023-06-15 17:49:19 -07:00
2023-04-12 11:48:22 -07:00
2023-04-12 11:48:22 -07:00
2023-06-08 09:34:41 -07:00
2023-05-19 12:16:24 -06:00
2023-06-05 14:13:18 -07:00
2023-04-29 19:52:57 -07:00
2023-01-17 17:40:39 -08:00
2022-12-27 09:41:39 +01:00
2023-02-10 10:29:26 +00:00

Tests

Tests that run on Travis have been split into jobs that run in their own VM in parallel. This reduces the overall running time but also is allowing recycling of a job when we get a flapper as opposed to have to recycle the whole test suite.

JetStream Tests

For JetStream tests, we need to observe a naming convention so that no tests are omitted when running on Travis.

The script runTestsOnTravis.sh will run a given job based on the definition found in ".travis.yml".

As for the naming convention:

  • All JetStream tests name should start with TestJetStream
  • Cluster tests should go into jetstream_cluster_test.go and start with TestJetStreamCluster
  • Super-cluster tests should go into jetstream_super_cluster_test.go and start with TestJetStreamSuperCluster

Not following this convention means that some tests may not be executed on Travis.