Skip to content

Fix cycle checking when calculating min delay from nearest physical action #4061

Fix cycle checking when calculating min delay from nearest physical action

Fix cycle checking when calculating min delay from nearest physical action #4061

Triggered via pull request February 4, 2025 19:51
Status Success
Total duration 28m 33s
Artifacts

all-targets.yml

on: pull_request
check-diff  /  check
26s
check-diff / check
/  ...  /  benchmark-tests
8m 44s
c / benchmarking / benchmark-tests
serialization  /  serialization-tests
10m 33s
serialization / serialization-tests
cpp  /  ...  /  benchmark-tests
cpp / cpp-benchmark-tests / benchmark-tests
cpp  /  ...  /  cpp-ros2-tests
cpp / cpp-ros2-tests / cpp-ros2-tests
rs  /  ...  /  benchmark-tests
rs / rs-benchmark-tests / benchmark-tests
ts  /  ...  /  benchmark-tests
ts / benchmarking / benchmark-tests
Matrix: c / ccpp / regular-tests
Matrix: c / default / regular-tests
Matrix: c / verifier / run
Matrix: cpp / cpp-tests / regular-tests
Waiting for pending jobs
Matrix: py / py-tests / regular-tests
Matrix: rs / rs-tests / regular-tests
Waiting for pending jobs
Matrix: ts / ts-tests / regular-tests
Waiting for pending jobs
Fit to window
Zoom out
Zoom in

Annotations

1 warning
c / benchmarking / benchmark-tests
Your workflow is using a version of actions/cache that is scheduled for deprecation, actions/cache@v2. Please update your workflow to use either v3 or v4 of actions/cache to avoid interruptions. Learn more: https://github.blog/changelog/2024-12-05-notice-of-upcoming-releases-and-breaking-changes-for-github-actions/#actions-cache-v1-v2-and-actions-toolkit-cache-package-closing-down