Closed minggangw closed 2 years ago
Removing the rclnodejs_test_msg compile steps will definitely simplify and improve CI reliability.
re: the action tests which are dependent on the fibonacci action msg in rclnodejs_test_msgs/action we can consider using the equivalent https://github.com/ros2/test_interface_files/tree/master/action. I believe the test_interface_files pkg is bundled in the ROS releases back to foxy.
re: https://github.com/RobotWebTools/rclnodejs/blob/develop/test/rclnodejs_test_msgs/msg/StaticArrayNonPrimitives.msg any thoughts on if/how we address test-non-primitive-static-array.js
For the test-non-primitive-static-arrary.js test, I don't find any .msg
that uses a Time
array in the current ROS2 release, so we may have to find something equivalent, maybe the JoyFeedbackArray.msg is suitable to replace? They are both kinds of primitives array, but we have to re-implement the case if we want to replace with it.
@minggangw let me confirm that addressing this issue involves the following actions:
pretest
script in package.json that currenctly calls compile_test.js scriptQ's:
I'll be glad to make any/all changes if you want to assign this issue to me.
remove test/rclnodejs_test_msgs/ folder
Yes
remove script/compile_tests.js note this script currently compiles: publisher_msg.cpp, subscription_msg.cpp, listener.cpp
add_two_ints_client.cpp will also be removed,
remove the pretest script in package.json that currenctly calls compile_test.js script
Yes
use fibonacci msg from test_interface_files pkg in place of rclnodejs_test_msgs pkg in the following tests: test-action-graph.js test-action-client.js test-action-server.js test/types/main.ts
We can depend on the CI to check if we miss some test cases, as there are so many.
clean up hacks in linux workflows to get around frequent env challenges when the rclnodejs_test_msgs pkg was built during testing
Yes, finally we can get rid of it :)
TBD - replace test-non-primitive-static-array.js with an equivalent test using a fixed size Array
If it's not easy to find an alternative, we can add this case into the blocklist
do we continue to support compiling the test/cpp/ project?
I suggest we will not to add them back in the future, we will focus on the JS case only.
@wayneparrott I have re-assigned this issue to you, please take your time, it's not urgent, thanks and stay healthy!
As these tests become unstable and cause the CI failures frequently, we decide to remove the C++ project used to verify some interactions with other ROS2 clients.