Skip to content

Reject zero-length TCP messages to prevent connection slot abuse (backport #71942) #158484

Reject zero-length TCP messages to prevent connection slot abuse (backport #71942)

Reject zero-length TCP messages to prevent connection slot abuse (backport #71942) #158484

Triggered via pull request June 3, 2026 19:06
Status Success
Total duration 1h 27m 17s
Artifacts 5

build.yaml

on: pull_request
Build on Linux (gcc_debug)
1h 10m
Build on Linux (gcc_debug)
Build on Linux (fake, gcc_release, clang, simulated)
1h 1m
Build on Linux (fake, gcc_release, clang, simulated)
Build on Linux (python_lib)
26m 40s
Build on Linux (python_lib)
Build on Linux (python lighting-app)
10m 16s
Build on Linux (python lighting-app)
Build on Darwin (clang, simulated)
0s
Build on Darwin (clang, simulated)
Build on Linux (coverage)
27m 28s
Build on Linux (coverage)
Fit to window
Zoom out
Zoom in

Annotations

16 warnings
Build on Linux (python lighting-app)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, buildjet/cache/restore@v4, buildjet/cache/save@v4, pyTooling/Actions/with-post-step@v0.4.5, Wandalen/wretry.action@v1.4.10_js_action. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 on Linux (python lighting-app)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
Build on Linux (python lighting-app)
Failed to save: Cache service responded with 409 during commit cache.
Build on Linux (python lighting-app)
Volume mount /:/runner-root-volume is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.
Build on Linux (python_lib)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, buildjet/cache/restore@v4, buildjet/cache/save@v4, pyTooling/Actions/with-post-step@v0.4.5, Wandalen/wretry.action@v1.4.10_js_action. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 on Linux (python_lib)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
Build on Linux (python_lib)
Volume mount /:/runner-root-volume is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.
Build on Linux (coverage)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, buildjet/cache/restore@v4, buildjet/cache/save@v4, pyTooling/Actions/with-post-step@v0.4.5, Wandalen/wretry.action@v1.4.10_js_action. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 on Linux (coverage)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
Build on Linux (fake, gcc_release, clang, simulated)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, buildjet/cache/restore@v4, buildjet/cache/save@v4, pyTooling/Actions/with-post-step@v0.4.5, tj-actions/changed-files@v46, Wandalen/wretry.action@v1.4.10_js_action. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 on Linux (fake, gcc_release, clang, simulated)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
Build on Linux (fake, gcc_release, clang, simulated)
Unexpected input(s) 'files-ignore', valid inputs are ['separator', 'include_all_old_new_renamed_files', 'old_new_separator', 'old_new_files_separator', 'files_from_source_file', 'files_from_source_file_separator', 'files', 'files_separator', 'files_yaml', 'files_yaml_from_source_file', 'files_yaml_from_source_file_separator', 'files_ignore_yaml', 'files_ignore_yaml_from_source_file', 'files_ignore_yaml_from_source_file_separator', 'files_ignore', 'files_ignore_separator', 'files_ignore_from_source_file', 'files_ignore_from_source_file_separator', 'sha', 'base_sha', 'since', 'until', 'path', 'quotepath', 'diff_relative', 'dir_names', 'dir_names_max_depth', 'dir_names_exclude_current_dir', 'dir_names_include_files', 'dir_names_include_files_separator', 'dir_names_deleted_files_include_only_deleted_dirs', 'json', 'escape_json', 'safe_output', 'fetch_depth', 'skip_initial_fetch', 'fetch_additional_submodule_history', 'since_last_remote_commit', 'write_output_files', 'output_dir', 'output_renamed_files_as_deleted_and_added', 'recover_deleted_files', 'recover_deleted_files_to_destination', 'recover_files', 'recover_files_separator', 'recover_files_ignore', 'recover_files_ignore_separator', 'token', 'api_url', 'use_rest_api', 'fail_on_initial_diff_error', 'fail_on_submodule_diff_error', 'negation_patterns_first', 'matrix', 'exclude_submodules', 'fetch_missing_history_max_retries', 'use_posix_path_separator', 'tags_pattern', 'tags_ignore_pattern']
Build on Linux (fake, gcc_release, clang, simulated)
Volume mount /:/runner-root-volume is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.
Build on Linux (gcc_debug)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/upload-artifact@v4, buildjet/cache/restore@v4, buildjet/cache/save@v4, pyTooling/Actions/with-post-step@v0.4.5, Wandalen/wretry.action@v1.4.10_js_action. Actions will be forced to run with Node.js 24 by default starting June 16th, 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 on Linux (gcc_debug)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
Build on Linux (gcc_debug)
Volume mount /:/runner-root-volume is going to mount '/' into the container which may cause file ownership change in the entire file system and cause Actions Runner to lose permission to access the disk.

Artifacts

Produced during runtime
Name Size Digest
bootstrap-logs-build_linux
212 KB
sha256:1b1cecff8fc6346b05ddf74e8f259137db543599abd8a669e8ba2d5eeb4a5d99
bootstrap-logs-build_linux_gcc_debug
212 KB
sha256:dd33f077ec656e8491969cca1622e523011d28b624f2710078f2d2b872e7d505
bootstrap-logs-build_linux_python_lib
212 KB
sha256:e7e0dfde07d2373b0f382cd8452bd4261ebb0af30a737af9671a0b42746f7523
bootstrap-logs-build_linux_python_lighting_device
213 KB
sha256:5d5ef1d6a24410fb1eb642e01bb8f759ac04e08da266b4105311b02a65cab729
bootstrap-logs-linux-
213 KB
sha256:5e98f69a624299441af9f9d70f0a8c5cc01ec309b47117a59ecdd6c8420cc631