Skip to content
.github/workflows/ros_test.yml

[Ninja][Dynamixel] workaround to use torque control via dynamixel api… #328

Sign in to view logs

[Ninja][Dynamixel] workaround to use torque control via dynamixel api…

[Ninja][Dynamixel] workaround to use torque control via dynamixel api… #328

Triggered via push November 16, 2024 14:19
@sugihara-16sugihara-16
pushed 5c2366e
develop/Ninja
Status Failure
Total duration 1h 25m 29s
Artifacts –

ros_test.yml

on: push
Matrix: ros_build_test
Fit to window
Zoom out
Zoom in

Annotations

3 errors and 3 warnings
ros_build_test (noetic, ubuntu:focal)
Process completed with exit code 1.
ros_build_test (one, ubuntu:jammy)
Process completed with exit code 1.
ros_build_test (melodic, ubuntu:bionic)
Process completed with exit code 1.
ros_build_test (noetic, ubuntu:focal)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ros_build_test (one, ubuntu:jammy)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
ros_build_test (melodic, ubuntu:bionic)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/