Skip to content

[Change] cron.daily: wire --maintenance after sigup; fix hardcoded lo… #231

[Change] cron.daily: wire --maintenance after sigup; fix hardcoded lo…

[Change] cron.daily: wire --maintenance after sigup; fix hardcoded lo… #231

Triggered via push March 31, 2026 13:08
Status Cancelled
Total duration 25m 24s
Artifacts 19

smoke-test.yml

on: push
Matrix: smoke-test / test
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 10 warnings
smoke-test / test (ubuntu2004)
The job has exceeded the maximum execution time of 25m0s
smoke-test / test (ubuntu2004)
The operation was canceled.
smoke-test / test (centos6)
The job has exceeded the maximum execution time of 25m0s
smoke-test / test (centos6)
The operation was canceled.
uat
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/upload-artifact@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
smoke-test / test (debian12)
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/upload-artifact@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
smoke-test / test (ubuntu2404)
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/upload-artifact@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
smoke-test / test (rocky10)
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/upload-artifact@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
yara-x
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/upload-artifact@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
smoke-test / test (centos7)
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/upload-artifact@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
smoke-test / test (rocky9)
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/upload-artifact@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
smoke-test / test (rocky8)
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/upload-artifact@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
smoke-test / test (ubuntu2004)
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/upload-artifact@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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/
smoke-test / test (centos6)
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/upload-artifact@v4, docker/build-push-action@v6, docker/setup-buildx-action@v3. 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
rfxn~linux-malware-detect~6QAOSY.dockerbuild
22.1 KB
sha256:fd6e798e4bf2fcc20a80dfca3da37d6cc6179703fd888894ea20b0db17ef46d8
rfxn~linux-malware-detect~BQKTPR.dockerbuild
21.5 KB
sha256:1b447ff4fe6489654d6db8b6c0f6fe1b14a1a6ecf65c41aa1dd095676b29345f
rfxn~linux-malware-detect~DD9JES.dockerbuild
23.6 KB
sha256:831aa08d4995f88c4741ab766c15d4c1ff2008624e01b269e4a378c6e8bdce1f
rfxn~linux-malware-detect~I2DUTB.dockerbuild
21.3 KB
sha256:7d1453e68182b4ab0cf46f283046cadc5d9d4e191cd6cc80608aa5d27a958e20
rfxn~linux-malware-detect~KDOMTI.dockerbuild
22 KB
sha256:ef1add6e5842af6b6e5e057848678c5aec0700051d9ea50a257004534d4675bc
rfxn~linux-malware-detect~N94SP9.dockerbuild
20.6 KB
sha256:a3ddc1194ac5d0633d47f83cf0e2dbb61762b4ed68bd90a642b11f4c56df3097
rfxn~linux-malware-detect~NU7ELV.dockerbuild
23.1 KB
sha256:03e952612abd5ec2e71939dbc70284398a0307aacf021b1b411f4fc49ef53f57
rfxn~linux-malware-detect~PC3C3A.dockerbuild
21.6 KB
sha256:77e8d6bb2b82e6bd498132ac4f83e0a56411f3aef35d40b019793ada219d1ef9
rfxn~linux-malware-detect~QO5KBR.dockerbuild
22.7 KB
sha256:77b77dc0478fb7e4a59ff2173984abdca10e7f184da6f05670b75fc5fc2c9b1e
rfxn~linux-malware-detect~VY47KL.dockerbuild
23.6 KB
sha256:f66e5f584fb51a3852229046ed7340521921691e46f1f25febe12b91d3f490d8
test-reports-lmd-centos6 Expired
136 Bytes
sha256:eab5312c3cd8cc5a7593b55a4e7daf66f4367803f88bfd0e46414b9ff375ad8f
test-reports-lmd-centos7 Expired
19.7 KB
sha256:4e530550c5a8468191cbe3e8f56721cf76dabf1c8d1de27b57bb878c7214d987
test-reports-lmd-debian12 Expired
19.6 KB
sha256:5dfe1a37007a8ebcbc707bc345b042ab49dc2d03f756ab78951859b492bf6d70
test-reports-lmd-rocky10 Expired
19.6 KB
sha256:03a9298e09039bedf03bec6736254eb3514758c00dc8e819f9096bc9675e07e7
test-reports-lmd-rocky8 Expired
19.7 KB
sha256:2474e32d943cd03d4d5a3cdbd4884bb3e04678692855e032937b8d176e5d3838
test-reports-lmd-rocky9 Expired
19.6 KB
sha256:9d641749e0dac30b22948ae506fb70c5645ddfc7f518fbe75a21e4dba570b6f6
test-reports-lmd-ubuntu2004 Expired
136 Bytes
sha256:7b381bc0ecaeae5fdb85f181c18f2a6a1ac8905dfe57d50524a784839f2e46b6
test-reports-lmd-ubuntu2404 Expired
19.8 KB
sha256:0b7fd3572a20d4b2369ab72a4eb994aff65ebf759fef94fbf2a18f91a67e53fa
test-reports-lmd-yara-x Expired
19.6 KB
sha256:d176031ac4ccb1ba4d07c81466d8b01ef6998398d7e44791bde26893de9a23dd