Files
nats-server/server
Ivan Kozlovic 67498af2dc [ADDED] LeafNode: Support for s2 compression
This is similar to PR #4115 but for LeafNodes.
Compression mode can be set on both side (the accept and in remotes).
```
leafnodes {
   port: 7422
   compression: s2_best
   remotes [
       {
         url: "nats://host2:74222"
         compression: s2_better
       }
   ]
}
```
Possible modes are similar than for routes (described in PR #4115),
except that when not defined we default to `s2_auto`.

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
2023-05-15 17:42:39 -06:00
..
2023-02-10 10:29:26 +00:00
2023-01-27 08:35:59 -08:00
2023-04-29 19:52:57 -07:00
2022-09-08 11:28:23 -06:00
2023-05-10 15:32:45 -07:00
2023-05-06 09:55:34 -07:00
2023-04-07 05:32:05 -07:00
2023-05-03 14:35:06 -06:00
2023-04-26 18:42:31 -07:00
2023-05-03 19:51:24 -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-04-07 05:32:05 -07:00
2023-05-03 19:51:24 -07:00
2023-02-28 15:17:24 -08:00
2023-02-10 10:29:26 +00:00
2023-02-10 10:29:26 +00:00
2023-05-12 21:04:51 -07:00
2023-04-29 19:52:57 -07:00
2023-05-12 12:38:20 -07:00
2023-05-09 20:11:53 -07:00
2023-04-12 11:48:22 -07:00
2023-04-12 11:48:22 -07:00
2023-05-10 15:31:54 -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
2023-05-03 19:51:24 -07: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.