Skip to content

fix two bugs mishandling fragmented frames (#508) #1212

fix two bugs mishandling fragmented frames (#508)

fix two bugs mishandling fragmented frames (#508) #1212

Triggered via push May 8, 2024 12:36
Status Failure
Total duration 1h 20m 46s
Artifacts 22

ci.yml

on: push
Matrix: Build
Matrix: ETW Plugin
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

7 errors and 4 warnings
Downlevel Functional Tests (1.0.2, 2019, Release, x64)
The self-hosted runner: dd028e7ec000000 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.
Downlevel Functional Tests (1.0.2, 2019, Release, x64)
The action 'Run Tests' has timed out after 15 minutes.
Downlevel Functional Tests (1.0.2, 2022, Release, x64)
The self-hosted runner: 70b4ba27c000000 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.
Downlevel Functional Tests (1.0.2, 2022, Release, x64)
The action 'Run Tests' has timed out after 15 minutes.
Downlevel Functional Tests (1.0.2, Prerelease, Release, x64)
The self-hosted runner: 980f45c5c000000 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.
Downlevel Functional Tests (1.0.2, Prerelease, Release, x64)
The action 'Run Tests' has timed out after 15 minutes.
Perf Tests (Prerelease, Release, x64)
The self-hosted runner: 966ba496c000000 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.
Build (2022, Release, x64) / Build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: microsoft/action-publish-symbols@719c40b80e38bca806f3e01e1e3dd3a67554cd68. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build (2022, Release, x64) / Build
The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/action-publish-symbols@719c40b80e38bca806f3e01e1e3dd3a67554cd68. 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) / Build
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: microsoft/action-publish-symbols@719c40b80e38bca806f3e01e1e3dd3a67554cd68. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
Build (2022, Debug, x64) / Build
The following actions uses node12 which is deprecated and will be forced to run on node16: microsoft/action-publish-symbols@719c40b80e38bca806f3e01e1e3dd3a67554cd68. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

Artifacts

Produced during runtime
Name Size
bin_Debug_x64
21.6 MB
bin_Release_x64
22.6 MB
etw_Debug
920 KB
etw_Release
919 KB
logs_downlevel_1.0.2_win2019_Release_x64
644 MB
logs_downlevel_1.0.2_win2022_Release_x64
279 MB
logs_downlevel_1.0.2_winPrerelease_Release_x64
276 MB
logs_func_win2019_Debug_x64
211 MB
logs_func_win2019_Release_x64
222 MB
logs_func_win2022_Debug_x64
289 MB
logs_func_win2022_Release_x64
278 MB
logs_func_winPrerelease_Debug_x64
267 MB
logs_func_winPrerelease_Release_x64
267 MB
logs_perf_win2019_Release_x64
85.5 MB
logs_perf_win2022_Release_x64
81.9 MB
logs_pktfuzz_win2022_Debug_x64
227 KB
logs_pktfuzz_win2022_Release_x64
177 KB
logs_stress_win2019_Debug_x64
240 MB
logs_stress_win2019_Release_x64
251 MB
logs_stress_win2022_Debug_x64
222 MB
logs_stress_win2022_Release_x64
223 MB
release_artifacts_Release_x64
12.8 MB