Skip to content

Nats v2 web

Nats v2 web #96

Triggered via pull request May 7, 2026 15:51
@sonus21sonus21
synchronize #295
nats-v2-web
Status Failure
Total duration 8m 17s
Artifacts 13

java-ci.yaml

on: pull_request
unit_test
2m 20s
unit_test
producer_only_test
2m 0s
producer_only_test
integration_test
6m 5s
integration_test
redis_cluster_test
3m 10s
redis_cluster_test
reactive_integration_test
6m 41s
reactive_integration_test
nats_integration_test
2m 0s
nats_integration_test
coverage_report
0s
coverage_report
Fit to window
Zoom out
Zoom in

Annotations

1 error and 7 warnings
nats_integration_test
Process completed with exit code 1.
build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, gradle/actions/setup-gradle@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
nats_integration_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
producer_only_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
unit_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
redis_cluster_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
integration_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
reactive_integration_test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-java@v4, actions/upload-artifact@v4, gradle/actions/setup-gradle@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
coverage-integration
747 KB
sha256:2e096ee19c4bf4138c6ce2fe748123b902f21a8092f8482db7846a2e61419440
coverage-nats
469 KB
sha256:cf294aadcd9ce08eee2cd04943947a70d5c21fb0d10c3a8fde5d3957fb766567
coverage-producer
317 KB
sha256:a0388f1ff3d3c329c731f3adafc474b51b795d2d722bdda1b6add76a3e4f21b3
coverage-reactive
575 KB
sha256:433e804ec06474da9fdc780b2b12b3fd4a0d2e322979e77993f6d1d1bb1d57bc
coverage-redis-cluster
530 KB
sha256:43dc413458b6cab5305acc8c5a85bdb9bf9e3505b60b233e0589e95f89304d4b
coverage-unit
513 KB
sha256:ba0ff75e0ab4ade4f5e1ac94a382f19c4b85bd8b138c0e15f7c7050bed3bfad4
integration-test-results
28.8 KB
sha256:d6c0c4e1ecb2848cc27c42f12abf66c9712febfd306bf37ac2629430d67bf3b3
nats-server-log
695 Bytes
sha256:6f299f3754eb687d463296534bf7d018d38dde9bc10307e1888595f441b1f6e9
nats-test-results
27.3 KB
sha256:38d85d46a916939cd32753f688ec51a95088134ae0dee5f9a9be01d965b6175a
producer-test-results
2.19 KB
sha256:550064d946e80d3f7c85e8e9daf71f48235f9b90988ad15ebe73f09558b72070
reactive-integration-test-results
27.3 KB
sha256:2fc1d3f92b02d6c5e03fe83a512f56e0b465a88bea8425411ea1ab4b1ad22342
redis-cluster-test-results
6.08 KB
sha256:34167fc633e54e9663724c3225ea3bee44de72ed1f03f25fbb71b640928458be
unit-test-results
40.7 KB
sha256:6d87f292fe5a0c6ecb3e13b5590a9b8ac16e5bbaa0b69e47b8e2f3c046e187d1