[Camera] Use appropriate data type for raw bytes data (#41208) #137057
build.yaml
on: push
Build on Linux (gcc_debug)
1h 4m
Build on Linux (fake, gcc_release, clang, simulated)
1h 43m
Build on Linux (python_lib)
24m 54s
Build on Linux (python lighting-app)
5m 35s
Build on Darwin (clang, simulated)
46m 0s
Build on Linux (coverage)
32m 14s
Annotations
11 warnings
|
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)
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)
`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)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
|
|
Build on Darwin (clang, simulated)
`pre` execution is not supported for local action from './.github/actions/checkout-submodules-and-bootstrap'
|
|
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.
|
|
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.
|