Skip to content
CI

Update eBPF version to 0.13.0 #942

Sign in to view logs

Update eBPF version to 0.13.0

Update eBPF version to 0.13.0 #942

Triggered via pull request December 13, 2023 20:11
@saxena-anuragsaxena-anurag
synchronize #426
saxena-anurag:user/anusa/update_ebpf_0_13
Status Cancelled
Total duration 41m 38s
Artifacts 19

ci.yml

on: pull_request
Matrix: Build
Matrix: ETW Plugin
Run Perf
3s
Run Perf
Matrix: Create Release Artifacts
Matrix: Downlevel Functional Tests
Matrix: Functional Tests
Matrix: Perf Tests
Matrix: Fuzz Packet Parsing
Matrix: Stress Tests
Complete
0s
Complete
Fit to window
Zoom out
Zoom in

Annotations

20 errors and 8 warnings
Stress Tests (2022, Debug, x64)
The action has timed out.
Stress Tests (2022, Release, x64)
The action has timed out.
Stress Tests (2019, Debug, x64)
The action has timed out.
Downlevel Functional Tests (1.0.0, 2019, Release, x64)
The action has timed out.
Downlevel Functional Tests (1.0.0, Prerelease, Release, x64)
The action has timed out.
Stress Tests (2019, Release, x64)
The action has timed out.
Functional Tests (2022, Release, x64)
The action has timed out.
Downlevel Functional Tests (1.0.0, 2022, Release, x64)
The action has timed out.
Functional Tests (2019, Release, x64)
The action has timed out.
Functional Tests (2019, Debug, x64)
The action has timed out.
Functional Tests (2022, Debug, x64)
The action has timed out.
Functional Tests (Prerelease, Release, x64)
The self-hosted runner: d31ecd38c000000 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Functional Tests (Prerelease, Debug, x64)
The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled.
Functional Tests (Prerelease, Debug, x64)
The self-hosted runner: d31ecd38c000001 lost communication with the server. Verify the machine is running and has a healthy network connection. Anything in your workflow that terminates the runner process, starves it for CPU/Memory, or blocks its network access can cause this error.
Perf Tests (2022, Release, x64)
Canceling since a higher priority waiting request for 'ci-426' exists
Perf Tests (2022, Release, x64)
The operation was canceled.
Perf Tests (2019, Release, x64)
Canceling since a higher priority waiting request for 'ci-426' exists
Perf Tests (2019, Release, x64)
The operation was canceled.
Perf Tests (Prerelease, Release, x64)
Canceling since a higher priority waiting request for 'ci-426' exists
Perf Tests (Prerelease, Release, x64)
The operation was canceled.
Build (2019, Release, x64)
The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/setup-msbuild@ab534842b4bdf384b8aaf93765dc6f721d9f5fab. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build (2019, Release, x64)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build (2019, Debug, x64)
The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/setup-msbuild@ab534842b4bdf384b8aaf93765dc6f721d9f5fab. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build (2019, Debug, x64)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build (2022, Debug, x64)
The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/setup-msbuild@ab534842b4bdf384b8aaf93765dc6f721d9f5fab. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build (2022, Debug, x64)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
Build (2022, Release, x64)
The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/setup-msbuild@ab534842b4bdf384b8aaf93765dc6f721d9f5fab. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build (2022, Release, x64)
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Artifacts

Produced during runtime
Name Size
bin_Debug_x64 Expired
94.7 MB
bin_Release_x64 Expired
90.4 MB
etw_Debug Expired
3.02 MB
etw_Release Expired
3.02 MB
logs_func_win2019_Debug_x64 Expired
291 MB
logs_func_win2019_Release_x64 Expired
287 MB
logs_func_win2022_Debug_x64 Expired
171 MB
logs_func_win2022_Release_x64 Expired
311 MB
logs_func_winPrerelease_Release_x64 Expired
186 MB
logs_perf_win2019_Release_x64 Expired
1.04 GB
logs_perf_win2022_Release_x64 Expired
1.07 GB
logs_perf_winPrerelease_Release_x64 Expired
980 MB
logs_pktfuzz_win2022_Debug_x64 Expired
1.2 MB
logs_pktfuzz_win2022_Release_x64 Expired
927 KB
logs_stress_win2019_Debug_x64 Expired
200 MB
logs_stress_win2019_Release_x64 Expired
268 MB
logs_stress_win2022_Debug_x64 Expired
211 KB
logs_stress_win2022_Release_x64 Expired
212 KB
release_artifacts_Release_x64 Expired
11.6 MB