[New] Pause/unpause: sentinel-based with duration, SIGSTOP for extern… #206
rfxnsmoke-test.yml
on: push
yara-x
21m 16s
uat
5m 0s
Matrix: smoke-test / test
Annotations
6 errors and 10 warnings
|
uat
Process completed with exit code 2.
|
|
smoke-test / test (rocky9)
Process completed with exit code 1.
|
|
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 (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 (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 (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 (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 (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~C71LK4.dockerbuild
|
21.7 KB |
sha256:1e817bcee84a435eed2cf2ae4f9938bf22936a2a170c2f8899f093734b6420f9
|
|
|
rfxn~linux-malware-detect~FLDE6Q.dockerbuild
|
20.9 KB |
sha256:64266a6508f3436dd606d007de0e07f784b06dc0e22b37033b4e34c19ea4111a
|
|
|
rfxn~linux-malware-detect~J4IXIB.dockerbuild
|
21.7 KB |
sha256:048b64f3bdc4a9dabd5da9852a09aa58b455a8cbf15f264c28f470948a26119f
|
|
|
rfxn~linux-malware-detect~M0J604.dockerbuild
|
22.8 KB |
sha256:92be8beff896cbfb98fc8abfdf5952d72c606290aef85eda4948b80ead9e109f
|
|
|
rfxn~linux-malware-detect~M0LSLC.dockerbuild
|
21.9 KB |
sha256:2148f7ad4a09e2b9abd7f6e2b982c1df2d95258981ff2f14b21971fcff895142
|
|
|
rfxn~linux-malware-detect~MA83B3.dockerbuild
|
20.1 KB |
sha256:1c06d90504be3a7f122d7b267b2a8b7ca50af1f50080e64d5e3712292a4405c7
|
|
|
rfxn~linux-malware-detect~NWYX39.dockerbuild
|
21.3 KB |
sha256:9e952249a08beca8ffa2ef434c6ffaff37278f27f53d0a4836f8dbb392c42642
|
|
|
rfxn~linux-malware-detect~Q7MNYU.dockerbuild
|
20.5 KB |
sha256:617f0d16d5a1d268411feed9cbbe6a33d4199c959ddb6bed0828cf1db66b0ca9
|
|
|
rfxn~linux-malware-detect~TWWSQY.dockerbuild
|
22.5 KB |
sha256:f26e598578f7c0de1e60d385bb92fd7c584bbc7b3aa7f4a1430f8fa6df08aae5
|
|
|
rfxn~linux-malware-detect~Z44B7Y.dockerbuild
|
21 KB |
sha256:8f458c8581a225b3c25db5039e7162bba7a23d816c0f3b354fd9d6bc62e1f2ea
|
|
|
test-reports-lmd-centos6
Expired
|
136 Bytes |
sha256:0c8870047817f648a44448c47e41417872aaf6c2c918ae976c8038a6e1517aab
|
|
|
test-reports-lmd-centos7
Expired
|
17.3 KB |
sha256:4378818982958cd111482305a2f14ba0a166fb9b34348a5eca84c17103dd5f8a
|
|
|
test-reports-lmd-debian12
Expired
|
17.3 KB |
sha256:3b7c365ac39077a64176640a5a2d2f7974ea508431e3efbaedbb7694213e1266
|
|
|
test-reports-lmd-rocky10
Expired
|
17.3 KB |
sha256:66f7b74e47909c7564fc4eb96ea28b5b926e06c3598d87869bd3953179273022
|
|
|
test-reports-lmd-rocky8
Expired
|
17.4 KB |
sha256:ec788a01b794eb66f4fc76cf8d0a86d848ed9c891ff4ffc658c63a71955b6dd7
|
|
|
test-reports-lmd-rocky9
Expired
|
23.6 KB |
sha256:c0908646d93a001b5768b2e580a394df1a919826078fe93803e258dc5c1cb42e
|
|
|
test-reports-lmd-ubuntu2004
Expired
|
136 Bytes |
sha256:9e3733f1b886bde08443825594da4cd953bf405d111fb1ab5618407ff4cb4405
|
|
|
test-reports-lmd-ubuntu2404
Expired
|
17.2 KB |
sha256:6047cb6a32643a057ead85cc384281023e339858003587bb558fa7efc97e3132
|
|
|
test-reports-lmd-yara-x
Expired
|
17.3 KB |
sha256:793577c92a12bea7cba0d094a1cc2b973cfcf405020ca102441dc4d19b27c78d
|
|