Skip to content

Nats backend

Nats backend #38

Triggered via pull request April 30, 2026 17:37
@sonus21sonus21
synchronize #292
nats-backend
Status Failure
Total duration 8m 18s
Artifacts 13

java-ci.yaml

on: pull_request
unit_test
2m 13s
unit_test
producer_only_test
1m 51s
producer_only_test
integration_test
6m 17s
integration_test
redis_cluster_test
3m 21s
redis_cluster_test
reactive_integration_test
6m 8s
reactive_integration_test
nats_integration_test
1m 49s
nats_integration_test
coverage_report
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/
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/
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
520 KB
sha256:c45f3128ff2b8615076ca68811a38a1a09fcf949c484759d1712c9839a036f55
coverage-nats
324 KB
sha256:d8a0ed346024196866d0d02bcab5fa03e52cd13ff6bc532fe8de8d49f6741d92
coverage-producer
286 KB
sha256:45416e0baf28b47352ee8aca7d405045b208f2d3d607dd7314ed9746f9edbc72
coverage-reactive
540 KB
sha256:f0502cf8c227d9aea0e9d9b4b0cc8cd7d664e38904a21fd5cf0e65a96fe8eae4
coverage-redis-cluster
489 KB
sha256:cdb75c7a0087420f1d31406d700f749b92cd2bea1226b5fa91868461feac40d4
coverage-unit
381 KB
sha256:144df35ebba83ee13efb65beac8de5ca05f696e6c5a4f1c31f411b2dc62e09ee
integration-test-results
26.5 KB
sha256:a296611e8ba2b04c421c3fbf691d057f7590661ea6cbf744210e2576ba334048
nats-server-log
695 Bytes
sha256:82d74badeb7c1a80171f4f25d4f646547ac7959ce0186c573f186fdaa2ab8282
nats-test-results
18.6 KB
sha256:b6900ca850da8dd3834a39c10d9cfd49d8c8f419391bc7697be0ed05a382d31b
producer-test-results
2.18 KB
sha256:910fb831215b3844a5a729b83524b2f5e4f5afd3f4a2bec40971e7756d03b7a6
reactive-integration-test-results
27.2 KB
sha256:26b5fc680f426aba95a5c682b4aebc7229c15dd04fd479dc19b26fb6341fae9d
redis-cluster-test-results
6.06 KB
sha256:5142fb654b1ae9ec0e18794cfcb3d7aecdc0407a7a9babae9e18fdf3ede3f092
unit-test-results
55.7 KB
sha256:c800059161060b7d93f28f57599670004a98bd7edfa52fb1ace2d2dd0929183d