Skip to content

[Fix] Unify progress output order: elapsed before eta in both foregro… #199

[Fix] Unify progress output order: elapsed before eta in both foregro…

[Fix] Unify progress output order: elapsed before eta in both foregro… #199

Triggered via push March 27, 2026 20:39
Status Cancelled
Total duration 25m 41s
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 (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 (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 (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 (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~1NU04R.dockerbuild
22.2 KB
sha256:1333beea494ec92e59db7ac4bc8d38d4ae2a44ba04a14f1185a4ded639d22d14
rfxn~linux-malware-detect~3YGJ0R.dockerbuild
21.3 KB
sha256:89b256be97fab3fe62fb02b2e3bd7b2de1e60417a1528ae04d68eb8ae5dbe642
rfxn~linux-malware-detect~5UFJCY.dockerbuild
20.7 KB
sha256:246a1b79b54e38a1e65fcf3b932a22b2b0ad27c3b53ef8f7fda3c7333c6b0344
rfxn~linux-malware-detect~8VTK49.dockerbuild
21.1 KB
sha256:2445fbbef90e7c543d7adf119ea1457192e4d48382f3ddc8711b08b8d7de82bf
rfxn~linux-malware-detect~IPMG3Z.dockerbuild
19.5 KB
sha256:e26811ea5b1dda1b419b82641f692c8394018aaa2e817343a4dafec333cff868
rfxn~linux-malware-detect~Q34RWL.dockerbuild
20.7 KB
sha256:de9f76a18521ef442b286123ab5921fa6ee4d043e355966e6e515ce9dacc8ea1
rfxn~linux-malware-detect~TP5SRK.dockerbuild
20 KB
sha256:c825863239a0a764858fc0b902dced990cca3c91f31a7ada28c595062ab1a9e6
rfxn~linux-malware-detect~ULAW1I.dockerbuild
22.6 KB
sha256:89a5c9afb8a8459e931713007b10a1607049a5e9a4549a04af52554130536bf1
rfxn~linux-malware-detect~XX6O9Q.dockerbuild
23 KB
sha256:f8e0cd1e67d143e9c99fa28e167d498ace3572f1c138c35148043e632ed91996
rfxn~linux-malware-detect~ZCAKL0.dockerbuild
21 KB
sha256:cd80b3447ad060ef6ab78aecbcb140a59191b74890fea8f5057f0f3ca2ef6c57
test-reports-lmd-centos6 Expired
136 Bytes
sha256:22dd4e28d41ea65a407d7cd3de39e0c714f47680402e9d93e3a6ee063d6ca4dc
test-reports-lmd-centos7 Expired
13.3 KB
sha256:0fc5cbfddc056e488409f03d09247f1329cf32351bba10342971333ed35dcf2b
test-reports-lmd-debian12 Expired
13.4 KB
sha256:76b1e96b3d9672fef6ec6dca594d8e301527b9e700b0d51ed0b86e2f835a6e80
test-reports-lmd-rocky10 Expired
13.3 KB
sha256:202f22c0e5c63285e077a56f91bf80814f7bf9acd0c351b955af71f7f8049cac
test-reports-lmd-rocky8 Expired
13.3 KB
sha256:c25ea6c3621c0df8676f63c590386a5993b15070ba642186436240fc3b3d6450
test-reports-lmd-rocky9 Expired
13.3 KB
sha256:cd48a90b10c90ec1a49fcc734ec92697070f027648f3ef12b2df6a5c87ef7142
test-reports-lmd-ubuntu2004 Expired
136 Bytes
sha256:860d0fd7ed4885df7c52120ddb48c6bde298c27d3b36aa0221070616f4df0699
test-reports-lmd-ubuntu2404 Expired
13.3 KB
sha256:33d19d7d51c1bed0a00f1febf61b0ebd9e10ce2b0c6f6668aac0d0e8b2795bf3
test-reports-lmd-yara-x Expired
13.3 KB
sha256:cae2f39cb1c0c4c4f2fedfb6bbf332b1b5e9e5388718d90aa54e95672bc18e83