Skip to content
test unit tests and sitl building

AP_RangeFinder: Move the flag setting location of has_data #42997

Sign in to view logs

AP_RangeFinder: Move the flag setting location of has_data

AP_RangeFinder: Move the flag setting location of has_data #42997

Triggered via pull request September 28, 2024 03:58
@peterbarkerpeterbarker
synchronize #26595
muramura:AP_Move_the_flag_setting_location_of_has_data
Status Success
Total duration 1h 35m 8s
Artifacts –

test_unit_tests.yml

on: pull_request
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

4 warnings
build (clang, unit-tests)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (base, unit-tests)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (base, sitl)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
build (clang, sitl)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/