Files
nats-server/server
R.I.Pienaar c24547eb4e Record the stream and consumer info timestamps (#4133)
This records the server time when info for streams and consumers are
created so that tools such as the nats cli can calculate time deltas for
last ack, last delivered and so forth in the context of the server
clock.

This will help aleviate problems with client devices experiencing clock
jitter that can show up in user interfaces as negative seconds since
last ack etc
2023-06-02 08:53:28 +03:00
..
2023-05-16 14:15:22 -06:00
2023-05-17 16:48:47 -07:00
2023-04-07 05:32:05 -07:00
2023-05-15 15:44:38 -07:00
2023-04-26 18:42:31 -07:00
2023-04-03 09:32:28 -06:00
2023-05-12 12:38:20 -07:00
2023-05-15 15:44:38 -07:00
2023-05-17 16:48:47 -07:00
2023-05-15 15:44:38 -07:00
2023-05-15 15:44:38 -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-17 19:27:58 -07:00
2023-05-19 12:16:24 -06:00
2023-04-29 19:52:57 -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.