Skip to content

[New] Exclude tests and dev files from release tarballs #217

[New] Exclude tests and dev files from release tarballs

[New] Exclude tests and dev files from release tarballs #217

Triggered via push March 28, 2026 19:52
Status Failure
Total duration 25m 39s
Artifacts 19

smoke-test.yml

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

Annotations

5 errors and 10 warnings
uat
Process completed with exit code 2.
smoke-test / test (centos6)
The job has exceeded the maximum execution time of 25m0s
smoke-test / test (centos6)
The operation was canceled.
smoke-test / test (ubuntu2004)
The job has exceeded the maximum execution time of 25m0s
smoke-test / test (ubuntu2004)
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 (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/
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/

Artifacts

Produced during runtime
Name Size Digest
rfxn~linux-malware-detect~0WC64V.dockerbuild
20.2 KB
sha256:8e2232676a2edc199b639eb1a9a67f6421a4af9c41ad54ad42f79a80d371d30c
rfxn~linux-malware-detect~2VURXS.dockerbuild
21.3 KB
sha256:def0977adc2fd03a145e89e3365dd557f0929478bf1d5fb216a5971de21681e8
rfxn~linux-malware-detect~4WLNUK.dockerbuild
22.5 KB
sha256:d9528c7af3dd0683b1cab675cafc27aedd160a46462b5a60e3ec8090a8a36779
rfxn~linux-malware-detect~7IX5QB.dockerbuild
23.8 KB
sha256:244ba8237af9d8bfacfe3b2710727dadae661cbfab141f145df2d9d183c4d4e3
rfxn~linux-malware-detect~CO6RRI.dockerbuild
21.8 KB
sha256:2f3e03a848f305ccbc4dac01d03fa6ec38ad7803cde401f846222526fa49a42d
rfxn~linux-malware-detect~K1BAI1.dockerbuild
21.9 KB
sha256:50a78b364ffb810ecf119b3a1516ef2d1abd37b00ac59c7c63fe4424c3fedbc9
rfxn~linux-malware-detect~O7UQL1.dockerbuild
19.9 KB
sha256:9a76abbc0a2cff7609709d7e88abe8abef35178fb1baf02cfd1496ee32b7d8c9
rfxn~linux-malware-detect~QMU4BA.dockerbuild
20.5 KB
sha256:cc6362f987a925de7517f99cb4b156b890a460783ef6d0259456cd7d3e5d5afe
rfxn~linux-malware-detect~WSE1EL.dockerbuild
22.3 KB
sha256:84783ecf8b7378a56dfa73526fc328579e08af790f2eed186da2725fa9fb64b5
rfxn~linux-malware-detect~Y4MMO4.dockerbuild
22.1 KB
sha256:81bba3cf176ca964378aad3b830ea92e81a44480140240a4bec5e1e8f4388848
test-reports-lmd-centos6 Expired
136 Bytes
sha256:068aa5705a52b32f9e33c08458c44dde15a8d753a61296a8242288a32811c194
test-reports-lmd-centos7 Expired
19.3 KB
sha256:d1fdbabfe6eefaf354a4adc7a2601313a230cce7fe69fe7152005c357dc369a1
test-reports-lmd-debian12 Expired
19.1 KB
sha256:0e115042da207c70b17c02a5e017e8d358a6b7179555caef676ee127acf5c925
test-reports-lmd-rocky10 Expired
19.2 KB
sha256:eb54f85725c7b91461daf9cd69e054ad776ab24f37cd3fa1318442106b86b69c
test-reports-lmd-rocky8 Expired
19.2 KB
sha256:8356e6b3363de595acb8d1af3b6e3952cdb92760bd23fdfaa892a2c2cef5245d
test-reports-lmd-rocky9 Expired
19.2 KB
sha256:fcbe7ed1d331c7af7e3ec20e1606d4a369416ad70b3a2c34fa117a64b9140f3d
test-reports-lmd-ubuntu2004 Expired
136 Bytes
sha256:3c97dc18a34b790db126be8c3a053cb1b1e0526fba3a969b2436f850319a4324
test-reports-lmd-ubuntu2404 Expired
19.2 KB
sha256:d0fffc14930c6f56ad5460ae21a87396903a7e31ca7e64e736d252004daafbb4
test-reports-lmd-yara-x Expired
19.2 KB
sha256:fc7c0c4ed51b8300247e363ac3292f2d5c81fa013ad632ce1ffd06632fbc9b17