Files
nats-server/server
Derek Collison 81541361dc Alternative fix for issue 4014, where we always send pings on ROUTER connections (#4016)
Alternative fix for issue
https://github.com/nats-io/nats-server/issues/4014: where we always send
pings for ROUTER, GATEWAY and LEAF spoke connections.

This is my own original work that I license to the project

[ x] Link to issue, e.g. Resolves #NNN
 Documentation added (if applicable)
 Tests added
[ x] Branch rebased on top of current main (git pull --rebase origin
main)
[ x] Changes squashed to a single commit (described
[here](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html))
[x] Build is green in Travis CI
[ x] You have certified that the contribution is your original work and
that you license the work to the project under the [Apache 2
license](https://github.com/nats-io/nats-server/blob/main/LICENSE)
Resolves #

Changes proposed in this pull request:
- in processPingTimer, add explicit test for ROUTER connection, and only
hold off sending ping based on receive ping
2023-04-05 20:16:22 -07:00
..
2023-01-27 10:43:30 +08:00
2022-07-05 09:33:12 +01:00
2023-02-28 15:36:37 +01:00
2022-01-21 11:03:19 -08:00
2023-01-12 10:31:32 +09:00
2022-09-08 11:28:23 -06:00
2023-04-04 15:15:24 -07:00
2023-04-03 21:08:59 -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
2023-04-04 14:43:46 -07:00
2022-11-14 08:28:19 -08:00
2023-01-12 10:31:32 +09:00
2023-04-02 03:52:43 -07:00
2023-03-30 15:02:59 -06:00
2022-04-01 17:55:33 -06:00
2023-04-03 14:46:57 -07:00
2023-02-28 20:43:46 -08:00
2023-02-28 20:43:46 -08:00
2023-03-30 15:02:59 -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
2021-09-01 14:55:26 -07:00
2022-07-05 09:28:00 +01:00
2023-04-03 21:08:59 -07: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.