Files
nats-server/server
Waldemar Quevedo 39185c11a6 Set max payload in gofuzz test (#3622)
* Set max payload in gofuzz test

This was causing the test to overrun mem limits due to max payload size
check being skipped in the parser when processing a `pub` protocol line.

Signed-off-by: Waldemar Quevedo <wally@nats.io>
2022-11-14 08:28:19 -08:00
..
2022-07-05 09:33:12 +01:00
2022-07-06 13:16:13 -07:00
2022-09-08 11:28:23 -06:00
2022-11-05 13:56:45 -07:00
2022-07-05 09:28:00 +01:00
2022-07-05 09:28:00 +01:00
2022-11-14 08:28:19 -08:00
2022-09-27 19:43:32 -06:00
2022-09-06 13:33:39 -07:00
2022-09-08 11:28:23 -06:00
2022-11-09 19:44:22 -08:00
2022-09-08 11:28:23 -06:00
2022-11-08 09:36:08 -07:00
2022-11-08 09:36:08 -07:00
2022-11-08 09:36:08 -07:00
2022-07-05 09:33:12 +01:00
2022-07-05 09:28:00 +01:00
2022-06-24 09:17:12 -07:00
2022-10-28 20:16:40 +05:00
2022-10-28 11:36:46 +05: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.