Skip to content

Nats backend

Nats backend #34

Triggered via pull request April 30, 2026 14:32
@sonus21sonus21
synchronize #292
nats-backend
Status Failure
Total duration 8m 4s
Artifacts 12

java-ci.yaml

on: pull_request
unit_test
2m 24s
unit_test
producer_only_test
2m 3s
producer_only_test
integration_test
5m 52s
integration_test
redis_cluster_test
3m 14s
redis_cluster_test
reactive_integration_test
6m 8s
reactive_integration_test
nats_integration_test
1m 59s
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/
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
520 KB
sha256:2d19b6030482eb734d87aac21ddfba0733e7567a615a0523c76c3ec8f4a3e3ca
coverage-nats
522 KB
sha256:baa6aba73615b70a355a96faa3e5d882cc4f777c882cbf6a33f919b94e610396
coverage-producer
287 KB
sha256:39778d8ca0564e6d06361210be7c90fef50bac3d88a8932b8b5cc31626d96b53
coverage-reactive
540 KB
sha256:afc49d7c61aa146efa6fc40e882193b8c74880e577c0359cbf0344a2fc6d7e1f
coverage-redis-cluster
489 KB
sha256:d1e0086657bfce55626576e0e775db7f6d8f6c6b261df4b8f112cd5187e21f19
coverage-unit
450 KB
sha256:f37e58df846328fb162c1c942d9988e20b447c62d5a56807e33c01e816d4f634
integration-test-results
26.4 KB
sha256:9ffa48a2fbdc2b502c83289603e35e7dd4251b8c64a3e861e432f448aaf11f63
nats-test-results
101 KB
sha256:18860b648c56c9160755d9bd9d485820150dc37d12c79ef86e18812452516764
producer-test-results
2.2 KB
sha256:7a8548f04206af2fbcf6bed913f5a8c53e446d1a70020e85c8d39d18a69c639e
reactive-integration-test-results
27.3 KB
sha256:f77730992537d49c9c4df11e7e06460bd1b66b8aac837a3a04d57ba45db80ccb
redis-cluster-test-results
6.06 KB
sha256:3b351f9de5ec49668ebba898a381119a5ed005cf6ea23a5be7588a9cb18b7346
unit-test-results
57.3 KB
sha256:2ca4ebe5a90a7cd2fa3f09fa80c63ed6885f49333aea3cba9f4020b08e84c39a