Skip to content
test unit tests and sitl building

GCS_MAVLink: Check if set_message_interval is too fast #43095

Sign in to view logs

GCS_MAVLink: Check if set_message_interval is too fast

GCS_MAVLink: Check if set_message_interval is too fast #43095

Triggered via pull request October 1, 2024 12:11
@stephendadestephendade
synchronize #28144
stephendade:loop-interval
Status Success
Total duration 20m 51s
Artifacts –

test_unit_tests.yml

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

Annotations

4 warnings
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 (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 (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/
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/