Skip to content

Nats scheduling fix (#297) #110

Nats scheduling fix (#297)

Nats scheduling fix (#297) #110

Triggered via push May 10, 2026 06:27
Status Success
Total duration 10m 0s
Artifacts 18

java-ci.yaml

on: push
Fit to window
Zoom out
Zoom in

Annotations

8 warnings
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/
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/
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/
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/
coverage_report
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/download-artifact@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
736 KB
sha256:bb0acf7aa317acae958516a5a634ef103ba318fbd8332aa18373ef533a6a999c
coverage-nats
315 KB
sha256:e0f0be016bd6950431ebb8b2abcaacea53f1bf03f876fe5fa03140ea44046114
coverage-producer
314 KB
sha256:575fdffe711187bde196be6a0fb3f676d4dcaec5e5be560f205523efc969f6b8
coverage-reactive
566 KB
sha256:62f99c34e25a780a71e12071e19fbd27217e7d3d66f86349907d9b9a92b884bb
coverage-redis-cluster
514 KB
sha256:c444dc761fa9b37541e607ede865ea81601de28ab3b77e63f3b2a46daee4e07c
coverage-report
1.35 MB
sha256:c8db72acc29776b46c80487c59755df807729d72d5cfe1ea2e059352f8f632d8
coverage-unit
513 KB
sha256:9ab37d818869cc7d0df188325628d6914708fed26b0c9c4133e03bdc6c575955
integration-redis-server
735 Bytes
sha256:ea092f08f7c5dbb2bc61d7f48d9dc4470104ebe733c81474d6626ec9c5d3db3e
integration-test-results
28.7 KB
sha256:3e65ce993eb860367b5ee3caa46fc3e655460eb7754e42165634bbd4951a238f
nats-server
855 Bytes
sha256:fb10aa95ee77f43b0f218d8c942ca88f9ac759a1a9bad86f7f83131fb51e95a2
nats-test-results
56.3 KB
sha256:f59e07df8819022ccf16248958486f3b4c2ed39451d4d393999c191f5cf9c656
producer-redis-server
602 Bytes
sha256:debd347f62b2674ded264754547b133c7f679de550c2637c8cddaee338157226
producer-test-results
2.19 KB
sha256:272b98e9fab8c2458051dd35ed83c3a36a4c62fbdb93e0010774d334ebdf70c6
reactive-integration-test-results
27.2 KB
sha256:27738f29e4150e073036704c065bf7d508af8df6e1677f5e229425e455cd5b17
reactive-redis-server
735 Bytes
sha256:a7bb2fa6de58070535d39766278dd1a4b54902ee7349cc4c323b46123d8c0263
redis-cluster-test-results
6.07 KB
sha256:2a38a00bedd55690bc0ef904f800a89df2c994abbc1294c8e996326920a07d7b
redis-server-cluster
8.07 KB
sha256:d2b6ad201a9259129014c0d87c1d7fde994e0714687352648ceec55c095c3647
unit-test-results
46 KB
sha256:dc1c1d696e530d7e1fbc7f2e02d8f737610aa13b26015f37f054d4707f920887