Files
nats-server/server
Ivan Kozlovic 7ff0ea449a Fixed issues with leafnode compression negotiation
When a server would send an asynchronous INFO to a remote server
it would incorrectly contain compression information that could
cause issues with one side thinking that the connection should
be compressed while the other side was not.

It also caused the authentication timer to be incorrectly set
which would cause a disconnect.

Signed-off-by: Ivan Kozlovic <ijkozlovic@gmail.com>
2023-06-09 13:20:44 -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
2023-06-05 14:13:18 -07:00
2022-09-08 11:28:23 -06:00
2023-06-07 14:31:53 -07:00
2023-06-09 09:29:13 -07:00
2023-06-02 16:45:07 -07:00
2023-05-15 15:44:38 -07:00
2023-04-26 18:42:31 -07:00
2023-06-04 13:30:15 -07:00
2022-11-14 08:28:19 -08:00
2023-04-03 09:32:28 -06:00
2023-05-12 12:38:20 -07:00
2023-06-02 13:19:22 +03:00
2023-06-03 18:17:28 -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-09 09:29:13 -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-06-05 14:13:18 -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.