Skip to content

[Fix] Checkpoint resume: allowlist gate + stopped scan visibility in … #236

[Fix] Checkpoint resume: allowlist gate + stopped scan visibility in …

[Fix] Checkpoint resume: allowlist gate + stopped scan visibility in … #236

Triggered via push April 4, 2026 06:07
Status Cancelled
Total duration 25m 23s
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 (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 (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 (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 (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 (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 (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 (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~72PC46.dockerbuild
23.4 KB
sha256:31d6fc66e1eef4576c1185e29f236294a47b82118cc97dea52105fa700979c1a
rfxn~linux-malware-detect~A6KR6L.dockerbuild
22.4 KB
sha256:24441bd2f0cc4e7482e3d1f378dffcba630b1d262e771dff1412ad9d4d443961
rfxn~linux-malware-detect~BO4WVK.dockerbuild
21.3 KB
sha256:83731331624529b01ff4811b7d85e30c476833df66858a2f2cd2515e83e49c50
rfxn~linux-malware-detect~GBMSTU.dockerbuild
21.3 KB
sha256:fb920dbe9e89dbaa870c9fc84e2718f0f969083330600fed9847fd0e86c99e16
rfxn~linux-malware-detect~LW3VEH.dockerbuild
21.9 KB
sha256:78ba827181cfb5c0ab3df984975d73244f4b618eac67af27bcdcabd3a3660772
rfxn~linux-malware-detect~P7HD8T.dockerbuild
23.2 KB
sha256:003966ea11d1fef7e33b3df98bfa6d0e97006c7e200ab52194c1344d14b2a71f
rfxn~linux-malware-detect~S3WPFF.dockerbuild
21.6 KB
sha256:72b643d44c3cac2d9bd0e2d996d8b34f880b0b8123f8c5d1500af3c356b8f06d
rfxn~linux-malware-detect~U8O52J.dockerbuild
20.2 KB
sha256:ba08f82f22fcd218b9784720f1766336433d6259fa50a7c45d87d85975e55542
rfxn~linux-malware-detect~UEECGS.dockerbuild
21.4 KB
sha256:7c3213a785294e596993856005cc59a2a8756da655b260ef9d0aa8d97d0534a9
rfxn~linux-malware-detect~Y021BK.dockerbuild
20.9 KB
sha256:55e81e060b95b178ef675d3851b09e8f4955ee1e8124cb07d1b405cf045441cc
test-reports-lmd-centos6 Expired
136 Bytes
sha256:1c6b6058e603cff58630abfb7eff10bfb87e83f9a603e5c1d088146883aaeee8
test-reports-lmd-centos7 Expired
19.8 KB
sha256:e80287c75746021e3cc29bfc7485b1bb13197b342c9b9d5d8dc5d2142bcff915
test-reports-lmd-debian12 Expired
19.7 KB
sha256:3a43b5c8ea8d46636090399609d0f3f1f63ec41f86e34102d8062547bc01a442
test-reports-lmd-rocky10 Expired
19.7 KB
sha256:15f22140802a55998bafbd7a9c58c74e3981dc259e147783c5d50fb6a07af05f
test-reports-lmd-rocky8 Expired
19.8 KB
sha256:a41b4499f4c0fceec7e3fe92a538a22483190b954b70e996e6f08727371014ef
test-reports-lmd-rocky9 Expired
19.7 KB
sha256:f2b0fe8068a34786bae8a82129f71935f2f6db12fef17963b176827b27b0cff6
test-reports-lmd-ubuntu2004 Expired
136 Bytes
sha256:1c6b6058e603cff58630abfb7eff10bfb87e83f9a603e5c1d088146883aaeee8
test-reports-lmd-ubuntu2404 Expired
19.7 KB
sha256:051008bbb26de5bba1b55e68a9f49cb5114f34c1dec7a06dd0d5803bf58ba286
test-reports-lmd-yara-x Expired
19.8 KB
sha256:c1598c8325fe20bce9b40d234d755cde41551ccbfe6fc50c58c4a54f4613a128