Files
nats-server/server
Neil ecbfac862c Ignore subject_transform_dest in stream sourcing (#4558)
This is a safer (less lines of code touched) alternative to #4557 for
now, which simply ignores the `subject_transform_dest` field in the API
and the stream assignments. We'll still look to merge the other PR to
clean up but will do so post-release when we have more time to test it.

Signed-off-by: Neil Twigg <neil@nats.io>
2023-09-19 18:10:01 +01:00
..
2023-08-02 11:25:48 -07:00
2023-07-18 12:21:31 -07:00
2023-06-03 10:03:23 +05:30
2023-06-05 14:13:18 -07:00
2023-09-18 13:53:25 -07:00
2021-11-15 17:23:08 -07:00
2023-09-17 10:01:24 -07:00
2022-11-14 08:28:19 -08:00
2023-06-27 20:41:57 -07:00
2023-06-02 13:19:22 +03:00
2023-09-12 07:52:17 -07:00
2023-08-21 15:55:00 -07:00
2023-08-31 15:52:00 -07:00
2023-07-21 16:56:13 -07:00
2023-09-05 14:39:28 -07:00
2023-09-12 17:19:30 -07:00
2023-08-30 14:54:30 -07:00
2023-08-02 11:25:48 -07:00
2023-08-04 10:15:35 -07:00
2023-04-12 11:48:22 -07:00
2023-08-02 11:25:48 -07:00
2023-09-04 16:54:36 +01: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-08-01 21:46:54 -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.