Skip to content

[WIP] feat(falco): experimental multi-thread support #3865

[WIP] feat(falco): experimental multi-thread support

[WIP] feat(falco): experimental multi-thread support #3865

Triggered via pull request April 22, 2026 13:26
Status Failure
Total duration 18m 29s
Artifacts 2

ci.yml

on: pull_request
fetch-version  /  fetch-version
44s
fetch-version / fetch-version
build-dev  /  build-and-test
2m 22s
build-dev / build-and-test
build-dev-minimal  /  build-and-test
1m 54s
build-dev-minimal / build-and-test
build-dev-minimal-arm64  /  build-and-test
2m 43s
build-dev-minimal-arm64 / build-and-test
build-dev-packages-arm64  /  build-modern-bpf-skeleton
1m 32s
build-dev-packages-arm64 / build-modern-bpf-skeleton
build-dev-packages-x86_64  /  build-modern-bpf-skeleton
1m 34s
build-dev-packages-x86_64 / build-modern-bpf-skeleton
build-dev-packages-arm64  /  build-musl-package
0s
build-dev-packages-arm64 / build-musl-package
build-dev-packages-arm64  /  build-wasm-package
0s
build-dev-packages-arm64 / build-wasm-package
build-dev-packages-arm64  /  build-win32-package
0s
build-dev-packages-arm64 / build-win32-package
build-dev-packages-arm64  /  build-macos-package
0s
build-dev-packages-arm64 / build-macos-package
build-dev-packages-x86_64  /  build-musl-package
7m 31s
build-dev-packages-x86_64 / build-musl-package
build-dev-packages-x86_64  /  build-wasm-package
2m 38s
build-dev-packages-x86_64 / build-wasm-package
build-dev-packages-x86_64  /  build-win32-package
6m 19s
build-dev-packages-x86_64 / build-win32-package
build-dev-packages-x86_64  /  build-macos-package
3m 4s
build-dev-packages-x86_64 / build-macos-package
check-engine-checksum
0s
check-engine-checksum
check-engine-version
0s
check-engine-version
build-dev-packages-arm64  /  build-packages-release
6m 26s
build-dev-packages-arm64 / build-packages-release
build-dev-packages-arm64  /  build-packages-debug
6m 4s
build-dev-packages-arm64 / build-packages-debug
build-dev-packages-arm64  /  build-packages-sanitizers
0s
build-dev-packages-arm64 / build-packages-sanitizers
build-dev-packages-x86_64  /  build-packages-release
16m 2s
build-dev-packages-x86_64 / build-packages-release
build-dev-packages-x86_64  /  build-packages-debug
7m 58s
build-dev-packages-x86_64 / build-packages-debug
build-dev-packages-x86_64  /  build-packages-sanitizers
6m 2s
build-dev-packages-x86_64 / build-packages-sanitizers
test-dev-packages-arm64  /  test-packages
test-dev-packages-arm64 / test-packages
test-dev-packages  /  test-packages
test-dev-packages / test-packages
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 15 warnings
build-dev-minimal / build-and-test
Process completed with exit code 2.
build-dev / build-and-test
Process completed with exit code 2.
build-dev-minimal-arm64 / build-and-test
Process completed with exit code 2.
build-dev-packages-x86_64 / build-wasm-package
Process completed with exit code 1.
build-dev-packages-x86_64 / build-macos-package
Process completed with exit code 2.
build-dev-packages-x86_64 / build-win32-package
Process completed with exit code 1.
build-dev-packages-x86_64 / build-musl-package
Process completed with exit code 2.
build-dev-packages-x86_64 / build-packages-sanitizers
Process completed with exit code 2.
build-dev-packages-arm64 / build-packages-debug
Process completed with exit code 2.
build-dev-packages-arm64 / build-packages-release
Process completed with exit code 2.
build-dev-packages-x86_64 / build-packages-debug
Process completed with exit code 2.
build-dev-packages-x86_64 / build-packages-release
Process completed with exit code 2.
fetch-version / fetch-version
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608. 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/
build-dev-minimal / build-and-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608. 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/
build-dev-packages-arm64 / build-modern-bpf-skeleton
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608, actions/upload-artifact@65c4c4a1ddee5b72f698fdd19549f0f0fb45cf08. 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/
build-dev-packages-x86_64 / build-modern-bpf-skeleton
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608, actions/upload-artifact@65c4c4a1ddee5b72f698fdd19549f0f0fb45cf08. 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/
build-dev / build-and-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608. 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/
build-dev-minimal-arm64 / build-and-test
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608. 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/
build-dev-packages-x86_64 / build-wasm-package
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608, actions/setup-node@5e21ff4d9bc1a8cf6de233a3057d20ec6b3fb69d. 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/
build-dev-packages-x86_64 / build-macos-package
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608. 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/
build-dev-packages-x86_64 / build-win32-package
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608. 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/
build-dev-packages-x86_64 / build-musl-package
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608. 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/
build-dev-packages-x86_64 / build-packages-sanitizers
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608, actions/download-artifact@fa0a91b85d4f404e444e00e005971372dc801d16. 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/
build-dev-packages-arm64 / build-packages-debug
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608, actions/download-artifact@fa0a91b85d4f404e444e00e005971372dc801d16. 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/
build-dev-packages-arm64 / build-packages-release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608, actions/download-artifact@fa0a91b85d4f404e444e00e005971372dc801d16. 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/
build-dev-packages-x86_64 / build-packages-debug
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608, actions/download-artifact@fa0a91b85d4f404e444e00e005971372dc801d16. 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/
build-dev-packages-x86_64 / build-packages-release
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135a41bc03ea155e62e844d188df1ea18608, actions/download-artifact@fa0a91b85d4f404e444e00e005971372dc801d16. 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
bpf_probe_aarch64.skel.h Expired
923 KB
sha256:738f73ff159479056c8656cc16223b9f76deca6c68cfa06fa49afa884d077ec8
bpf_probe_x86_64.skel.h Expired
1 MB
sha256:334a3ed59f7ca117734a3f55add774ef28a6bfe67b9507308bb892f7162044a8