Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FastRTPS/Connext Action tests are suspiciously short, and probably don't work #319

Open
sloretz opened this issue Dec 7, 2018 · 2 comments
Labels
backlog bug Something isn't working Connext Connext support FastRTPS FastRTPS support

Comments

@sloretz
Copy link
Contributor

sloretz commented Dec 7, 2018

Bug report

Required Info:

Steps to reproduce issue

  1. Run the action test using rclcpp with fastrtps and connext
colcon test --event-handlers console_direct+ --packages-select test_communication --ctest-args -R test_action_client_server__Fibonacci__rclcpp__rmw_fastrtps_cpp__rmw_connext_cpp
  1. Run the executables the above test should be running on their own
    RMW_IMPLEMENTATION=rmw_fastrtps_cpp ./build/test_communication/test_action_client_cpp Fibonacci /foo/bar
    
    RMW_IMPLEMENTATION=rmw_connext_cpp ./build/test_communication/test_action_server_cpp Fibonacci /foo/bar
    

Expected behavior

  1. The test would pass, taking about a second or so, and outputting info about goals and feedback
  2. Run independently the tests should output information about goals and feedback

Actual behavior

  1. The test passes in 0.1 seconds with no output
  2. Run independently the client says it sent a goal, but the server does not print a message saying it received it.

Additional information

Same behavior if the rmw implementations are flipped so it's a connext client with fastrtps server. If both are fastrtps or both are connext it works as expected. The service/client and subscriber/publisher tests appear to work fine across fastrtps and connext.

@sloretz sloretz added the bug Something isn't working label Dec 7, 2018
@sloretz sloretz self-assigned this Dec 7, 2018
@sloretz
Copy link
Contributor Author

sloretz commented Dec 7, 2018

It looks like all cross vendor tests are skipped if they involve services. If that's still the right thing to do, then it would make sense to skip action across vendors too since they use services.

# TODO different vendors can't talk to each other right now
if(NOT rmw_implementation1 STREQUAL rmw_implementation2 AND
(NOT(rmw_implementation1 MATCHES "(.*)connext(.*)" AND rmw_implementation2 MATCHES "(.*)connext(.*)"))
)
set(SKIP_TEST "SKIP_TEST")
endif()

@sloretz sloretz removed their assignment Feb 14, 2019
@chapulina chapulina added Connext Connext support FastRTPS FastRTPS support labels Nov 4, 2020
@clalancette
Copy link
Contributor

It looks like all cross vendor tests are skipped if they involve services. If that's still the right thing to do, then it would make sense to skip action across vendors too since they use services.

Yeah, as far as I know, services don't currently work cross-vendor. So I think disabling cross-vendor action testing is the correct thing to do here as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog bug Something isn't working Connext Connext support FastRTPS FastRTPS support
Projects
None yet
Development

No branches or pull requests

3 participants