Skip to content

(2.6 patch) Fix recvfrom never populating from_addr due to fromlen being zero #1827

(2.6 patch) Fix recvfrom never populating from_addr due to fromlen being zero

(2.6 patch) Fix recvfrom never populating from_addr due to fromlen being zero #1827

Triggered via pull request October 14, 2024 01:49
Status Cancelled
Total duration 2m 47s
Artifacts

ci.yml

on: pull_request
validate_imported_protos  /  Validate Imported Proto Files
14s
validate_imported_protos / Validate Imported Proto Files
validate_python  /  Validate Python Code
1m 28s
validate_python / Validate Python Code
Matrix: create_client_artifacts / build
cancel_builds  /  Cancel Build(s)
2s
cancel_builds / Cancel Build(s)
Matrix: build_desktop / build
build_nilrt  /  NILRT Cross Compile with GCC 6.3.0
1m 3s
build_nilrt / NILRT Cross Compile with GCC 6.3.0
run_ubuntu_system_tests  /  Run Tests
run_ubuntu_system_tests / Run Tests
run_win_system_tests  /  Run Tests
run_win_system_tests / Run Tests
create_release  /  Create Release
create_release / Create Release
Fit to window
Zoom out
Zoom in

Annotations

6 errors and 2 warnings
build_desktop / Ubuntu Build
The run was canceled by @github-actions[bot].
build_desktop / Ubuntu Build
The operation was canceled.
build_desktop / Windows Build
The run was canceled by @github-actions[bot].
build_desktop / Windows Build
The operation was canceled.
build_nilrt / NILRT Cross Compile with GCC 6.3.0
The run was canceled by @github-actions[bot].
build_nilrt / NILRT Cross Compile with GCC 6.3.0
The operation was canceled.
cancel_builds / Cancel Build(s)
The following actions uses node12 which is deprecated and will be forced to run on node16: styfle/[email protected]. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
cancel_builds / Cancel Build(s)
The following actions use a deprecated Node.js version and will be forced to run on node20: styfle/[email protected]. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/