Add sample of AF_XDP socket usage in a restricted process #2888
mtfriesenci.yml
on: pull_request
Matrix: Build / build_matrix
Resolve base commit reference
9s
Matrix: OneBranch Build Validation
Matrix: RX Filter Perf Tests
Matrix: Build AllPackage
Matrix: Create Release Artifacts
Matrix: Downlevel Functional Tests
Matrix: Functional Tests
Matrix: Fuzz Packet Parsing
Matrix: Ring Perf Tests
Matrix: Stress Tests
Matrix: XskFwdKm Test
Matrix: XskRestricted Test
Matrix: Build (Base Ref) / build_matrix
Matrix: XSK Perf Tests
Complete
4s
Perf Test Summary
0s
Annotations
32 errors and 12 warnings
|
OneBranch Build Validation (Release, arm64)
Canceling since a higher priority waiting request for ci-980 exists
|
|
OneBranch Build Validation (Release, arm64)
The operation was canceled.
|
|
OneBranch Build Validation (Debug, arm64)
Canceling since a higher priority waiting request for ci-980 exists
|
|
OneBranch Build Validation (Debug, arm64)
The operation was canceled.
|
|
Build / Build / Build arm64_Release_2022
Canceling since a higher priority waiting request for ci-980 exists
|
|
Build / Build / Build arm64_Release_2022
The operation was canceled.
|
|
Build (Base Ref) / Build main / Build arm64_Release_2022
Canceling since a higher priority waiting request for ci-980 exists
|
|
Build (Base Ref) / Build main / Build arm64_Release_2022
The operation was canceled.
|
|
Build (Base Ref) / Build main / Build arm64_Debug_2022
Canceling since a higher priority waiting request for ci-980 exists
|
|
Build (Base Ref) / Build main / Build arm64_Debug_2022
The operation was canceled.
|
|
Build (Base Ref) / Build main / Build x64_Debug_2022
Canceling since a higher priority waiting request for ci-980 exists
|
|
Build (Base Ref) / Build main / Build x64_Debug_2022
The operation was canceled.
|
|
Build / Build / Build arm64_Debug_2022
Canceling since a higher priority waiting request for ci-980 exists
|
|
Build / Build / Build arm64_Debug_2022
The operation was canceled.
|
|
Build / Build / Build x64_Debug_2022
Canceling since a higher priority waiting request for ci-980 exists
|
|
Build / Build / Build x64_Debug_2022
The operation was canceled.
|
|
Build / Build / Build x64_Release_2022
Canceling since a higher priority waiting request for ci-980 exists
|
|
Build / Build / Build x64_Release_2022
The operation was canceled.
|
|
Build (Base Ref) / Build main / Build x64_Release_2022
Canceling since a higher priority waiting request for ci-980 exists
|
|
Build (Base Ref) / Build main / Build x64_Release_2022
The operation was canceled.
|
|
Complete
Process completed with exit code 1.
|
|
CI
Canceling since a higher priority waiting request for ci-980 exists
|
|
CI
Canceling since a higher priority waiting request for ci-980 exists
|
|
CI
Canceling since a higher priority waiting request for ci-980 exists
|
|
CI
Canceling since a higher priority waiting request for ci-980 exists
|
|
CI
Canceling since a higher priority waiting request for ci-980 exists
|
|
CI
Canceling since a higher priority waiting request for ci-980 exists
|
|
CI
Canceling since a higher priority waiting request for ci-980 exists
|
|
CI
Canceling since a higher priority waiting request for ci-980 exists
|
|
CI
Canceling since a higher priority waiting request for ci-980 exists
|
|
CI
Canceling since a higher priority waiting request for ci-980 exists
|
|
CI
Canceling since a higher priority waiting request for ci-980 exists
|
|
OneBranch Build Validation (Release, x64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@6fb02220983dee41ce7ae257b6f4d8f9bf5ed4ce. 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/
|
|
OneBranch Build Validation (Debug, x64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@6fb02220983dee41ce7ae257b6f4d8f9bf5ed4ce. 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/
|
|
OneBranch Build Validation (Release, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@6fb02220983dee41ce7ae257b6f4d8f9bf5ed4ce. 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/
|
|
OneBranch Build Validation (Debug, arm64)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@6fb02220983dee41ce7ae257b6f4d8f9bf5ed4ce. 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/
|
|
Build / Build / Build arm64_Release_2022
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@6fb02220983dee41ce7ae257b6f4d8f9bf5ed4ce. 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/
|
|
Build (Base Ref) / Build main / Build arm64_Release_2022
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@6fb02220983dee41ce7ae257b6f4d8f9bf5ed4ce. 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/
|
|
Build (Base Ref) / Build main / Build arm64_Debug_2022
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@6fb02220983dee41ce7ae257b6f4d8f9bf5ed4ce. 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/
|
|
Build (Base Ref) / Build main / Build x64_Debug_2022
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@6fb02220983dee41ce7ae257b6f4d8f9bf5ed4ce. 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/
|
|
Build / Build / Build arm64_Debug_2022
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@6fb02220983dee41ce7ae257b6f4d8f9bf5ed4ce. 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/
|
|
Build / Build / Build x64_Debug_2022
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@6fb02220983dee41ce7ae257b6f4d8f9bf5ed4ce. 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/
|
|
Build / Build / Build x64_Release_2022
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@6fb02220983dee41ce7ae257b6f4d8f9bf5ed4ce. 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/
|
|
Build (Base Ref) / Build main / Build x64_Release_2022
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: microsoft/setup-msbuild@6fb02220983dee41ce7ae257b6f4d8f9bf5ed4ce. 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 | |
|---|---|---|---|
|
onebranch_bin_Debug_x64
|
6.67 MB |
sha256:a39a6caad39746d3883175b9346522f9c3c783f6d5d7f5c929427fa57438af3d
|
|
|
onebranch_bin_Release_x64
|
6.02 MB |
sha256:0e14a8ebb101b7a7f0092eabb269e56079f1372df4818a80de83d2ef2384136c
|
|