Files
nats-server/server
Jean-Noël Moyne 003daf3db8 Fixes possible message duplication in sourcing streams if upgrading to 2.10 and then back down to 2.9
2.10 adds a couple space separated fields to the sourcing message header from 2 to 4 but the current 2.9 code is too strict of checking the number of fields is exactly 2 rather than at least 2

Signed-off-by: Jean-Noël Moyne <jnmoyne@gmail.com>
2023-08-30 15:27:26 -07:00
..
2023-08-02 11:25:48 -07:00
2023-01-27 10:43:30 +08:00
2022-07-05 09:33:12 +01:00
2023-06-05 13:02:05 -07:00
2022-01-21 11:03:19 -08:00
2022-09-08 11:28:23 -06:00
2023-08-25 11:04:37 -07:00
2021-11-15 17:23:08 -07:00
2022-07-05 09:28:00 +01:00
2021-11-15 17:23:08 -07:00
2022-07-05 09:28:00 +01:00
2020-02-25 19:53:09 -05:00
2023-08-21 22:03:26 +01:00
2023-08-21 22:03:26 +01:00
2022-11-14 08:28:19 -08:00
2023-06-02 13:19:22 +03:00
2023-07-21 16:56:13 -07:00
2023-07-21 16:56:13 -07:00
2023-08-02 11:25:48 -07:00
2023-08-02 11:25:48 -07:00
2023-03-30 15:02:59 -06:00
2020-06-12 10:03:47 -06:00
2023-04-12 11:48:22 -07:00
2023-04-12 11:48:22 -07:00
2023-08-02 08:51:08 -07:00
2023-08-02 11:25:48 -07:00
2018-10-06 14:06:14 -07:00
2023-06-05 22:41:09 +03:00
2021-11-15 17:23:08 -07:00
2021-11-15 17:23:08 -07:00
2023-07-21 16:56:13 -07:00
2022-07-05 09:33:12 +01:00
2021-09-01 14:55:26 -07:00
2022-07-05 09:28:00 +01:00
2019-12-12 11:58:24 -07:00
2023-08-17 15:28:48 +01:00
2022-03-25 12:11:55 -06: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.