Files
nats-server/server
Ivan Kozlovic 79ca0c1787 Move test to "norace_test.go"
The test TestJetStreamClusterConsumerListPaging was in the
jetstream_cluster_3_test.go and because of `-race` flag would
take more than 440 seconds (7+ minutes) as seen here:

https://app.travis-ci.com/github/nats-io/nats-server/jobs/593984385#L335

Without the `-race` flag, this test takes ~17 seconds.

Signed-off-by: Ivan Kozlovic <ivan@synadia.com>
2023-01-23 17:05:18 -07:00
..
2022-07-05 09:33:12 +01:00
2022-01-21 11:03:19 -08:00
2023-01-12 10:31:32 +09:00
2023-01-12 10:31:32 +09:00
2022-09-08 11:28:23 -06:00
2023-01-06 12:40:19 -05: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
2023-01-12 10:31:32 +09:00
2022-11-14 08:28:19 -08:00
2023-01-12 10:31:32 +09:00
2022-03-17 17:53:06 -06:00
2022-12-31 18:50:46 -08:00
2022-04-01 17:55:33 -06:00
2023-01-23 17:05:18 -07:00
2022-12-06 06:45:00 -05:00
2022-03-17 17:53:06 -06:00
2021-11-15 17:23:08 -07:00
2021-11-15 17:23:08 -07:00
2022-07-05 09:33:12 +01:00
2022-07-05 09:28:00 +01:00
2022-10-28 20:16:40 +05: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.