Skip to content

[Fix] Production audit: purge dotfile glob, quarantine PID, temp leak… #180

[Fix] Production audit: purge dotfile glob, quarantine PID, temp leak…

[Fix] Production audit: purge dotfile glob, quarantine PID, temp leak… #180

Triggered via push March 25, 2026 04:56
Status Cancelled
Total duration 22m 45s
Artifacts 19

smoke-test.yml

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

Annotations

17 errors and 10 warnings
smoke-test / test (debian12)
Canceling since a higher priority waiting request for lmd-refs/heads/2.0.1-debian12 exists
smoke-test / test (debian12)
The operation was canceled.
smoke-test / test (ubuntu2404)
Canceling since a higher priority waiting request for lmd-refs/heads/2.0.1-ubuntu2404 exists
smoke-test / test (rocky8)
Canceling since a higher priority waiting request for lmd-refs/heads/2.0.1-rocky8 exists
smoke-test / test (ubuntu2404)
The operation was canceled.
smoke-test / test (rocky8)
The operation was canceled.
smoke-test / test (rocky10)
Canceling since a higher priority waiting request for lmd-refs/heads/2.0.1-rocky10 exists
smoke-test / test (rocky10)
The operation was canceled.
smoke-test / test (centos6)
Canceling since a higher priority waiting request for lmd-refs/heads/2.0.1-centos6 exists
smoke-test / test (centos6)
The operation was canceled.
smoke-test / test (rocky9)
Canceling since a higher priority waiting request for lmd-refs/heads/2.0.1-rocky9 exists
smoke-test / test (rocky9)
The operation was canceled.
smoke-test / test (centos7)
Canceling since a higher priority waiting request for lmd-refs/heads/2.0.1-centos7 exists
smoke-test / test (centos7)
The operation was canceled.
smoke-test / test (ubuntu2004)
Canceling since a higher priority waiting request for lmd-refs/heads/2.0.1-ubuntu2004 exists
smoke-test / test (ubuntu2004)
The operation was canceled.
yara-x
Process completed with exit code 1.
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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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~6KW07R.dockerbuild Expired
20.3 KB
sha256:88faf186d30cc5305436c6761276c498cbcad22aa3448e13c38d3bd9599756a0
rfxn~linux-malware-detect~ANJL4M.dockerbuild Expired
20.5 KB
sha256:1553ec97ba726f35f3385cc59feb6d8acf05ddddc80a010836aa6b6c717c5588
rfxn~linux-malware-detect~ATLGNZ.dockerbuild Expired
21.6 KB
sha256:4609a76760b52e6a22f83bdd47badd7e3f8ec6d80fcfd995540775b8b0c41bb6
rfxn~linux-malware-detect~EGH0HZ.dockerbuild Expired
21.8 KB
sha256:b5c82bdf86611292242e45b1561360609dc16961ebad91d833702901c51c2143
rfxn~linux-malware-detect~EZEIFV.dockerbuild Expired
21 KB
sha256:2bf81d8a8081352e562e3713e867dab8e1486ce13d8a45b37d99e482af5c416e
rfxn~linux-malware-detect~M15YFG.dockerbuild Expired
21.2 KB
sha256:3ad75cac56f5601f80f01308c259bc800311180e4f5b573919c31164a0246e43
rfxn~linux-malware-detect~OE0KGE.dockerbuild Expired
23.2 KB
sha256:bf2ca07116d6274467dffa9dd0d0b2d9488854fe6b11f84a0cc12bb2f5529a3b
rfxn~linux-malware-detect~OFMWHS.dockerbuild Expired
23.3 KB
sha256:188d3ac2f65fef2adc08394ccf2ad243e0efb73b8ae85fd85f1fd9df5872e9a9
rfxn~linux-malware-detect~P0MS2M.dockerbuild Expired
19.8 KB
sha256:185df19a6933fccdf0a9359205c2a38d9ad60dc5ac111993149d00f1f906ecdb
rfxn~linux-malware-detect~UE4Y81.dockerbuild Expired
22.4 KB
sha256:91aaf03f363dd0cdd70b098d27686e178cc92b650ba7947eb3e3f65a861005c6
test-reports-lmd-centos6 Expired
136 Bytes
sha256:a029bd336b417815abf55cc3652c365b2c79f503acd92528304900722c451017
test-reports-lmd-centos7 Expired
136 Bytes
sha256:296b75a2e2b9f43755e61db10a181459c52c9f3e76126aa88ee9c5b8daa30993
test-reports-lmd-debian12 Expired
136 Bytes
sha256:5bb610de2e98a77dc94e90a71e26fbb5896e411b39979ed262d8cd2f645897ca
test-reports-lmd-rocky10 Expired
136 Bytes
sha256:a0b3af342b22493b1e6c6a45ae2f440301be84df423af1f8aca8a3ab55a84b88
test-reports-lmd-rocky8 Expired
136 Bytes
sha256:ad663ac68e579f6bfc536bee82c0e29e5e755731fe0826458b5ad9e0c3c8eb6e
test-reports-lmd-rocky9 Expired
136 Bytes
sha256:c664899678d37dc8934fe613e65c61d9b4a929d495f012d2ffbc39786266b509
test-reports-lmd-ubuntu2004 Expired
136 Bytes
sha256:8aca110698fcfa256f3f70749d95f68ecff9615af3d884a0424bb60e86db0f42
test-reports-lmd-ubuntu2404 Expired
136 Bytes
sha256:014b83bb41ba8abcabb8ede347f67855dff44ac2ea9957ad86e83128ef769bc5
test-reports-lmd-yara-x Expired
14.6 KB
sha256:9c0d7ed11eb662bdf9f28814e5b0ce19a5406d0ba8e9bc66ca99293f28c13d5a