Files
nats-server/server
Derek Collison 3173d435b1 Initial support for zOS (#4209)
zOS is an IBM Z (mainframe) operating system. In the days of yore, it
was MVS.

 - [ ] 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 - the inability to build on zOS.

### Changes proposed in this pull request:

 - This PR adds a couple of files to allow building nats-server on zOS.
2023-07-18 12:21:31 -07:00
..
2023-06-22 12:25:54 -07:00
2023-02-10 10:29:26 +00:00
2023-07-18 12:21:31 -07:00
2023-06-03 10:03:23 +05:30
2023-05-16 14:15:22 -06:00
2023-06-05 14:13:18 -07:00
2023-07-13 07:29:40 -07:00
2023-07-13 16:04:11 -04:00
2023-06-09 09:29:13 -07:00
2023-06-10 20:56:42 -07:00
2023-07-12 09:06:44 -07:00
2023-04-03 09:32:28 -06:00
2023-06-27 20:41:57 -07:00
2023-06-02 13:19:22 +03:00
2023-07-17 10:41:51 -07:00
2023-05-15 15:44:38 -07:00
2023-07-11 14:36:10 -07:00
2023-07-11 14:36:10 -07:00
2023-02-10 10:29:26 +00:00
2023-02-10 10:29:26 +00:00
2023-05-15 15:44:38 -07:00
2023-06-28 17:48:53 -07:00
2023-07-13 07:29:40 -07:00
2023-07-13 07:29:40 -07:00
2023-07-17 10:41:51 -07:00
2023-06-22 12:25:54 -07:00
2023-04-12 11:48:22 -07:00
2023-04-12 11:48:22 -07:00
2023-06-08 09:34:41 -07:00
2023-05-19 12:16:24 -06:00
2023-07-11 19:45:39 -07: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-02-10 10:29:26 +00: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.