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

Allocator test isn't working well with opensplice and fastrtps #73

Open
ivanpauno opened this issue Apr 1, 2019 · 0 comments
Open

Allocator test isn't working well with opensplice and fastrtps #73

ivanpauno opened this issue Apr 1, 2019 · 0 comments
Labels
bug Something isn't working

Comments

@ivanpauno
Copy link
Member

Bug report

  • Operating System:
    Ubuntu 18.04
  • Installation type:
    From source
  • Version or commit hash:
    a9f131b (realtime_support)
  • DDS implementation:
    Opensplice and FastRTPS
  • Client library (if applicable):
    rclcpp

Steps to reproduce issue

  • Checkout rclcpp branch ivanpauno/fix_issue_#668 (4b23cf464dca6feb42f84c0a8cfb1afb74ac1231)
  • Rebuild rclcpp and test_tlsf
colcon build --symlink-install --packages-up-to rclcpp test_tlsf
  • Run test_tlsf
colcon test --packages-select test_tlsf

Expected behavior

The allocator_unique_ptr test fail for the three vendors.

Actual behavior

It's only failing in connext and passing in fastrtps and opensplice, when it shouldn't.

Additional information

This stack trace:

/home/ivanpauno/ros2_ws/build/tlsf_cpp/test_tlsf__rmw_opensplice_cpp : operator new(unsigned long)+0x3b

Is marked as match in check_stacktrace.
only because it contains opensplice in the test name. The same happens with fastrtps. It's not happening with connext, as is not part of the token list.

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

No branches or pull requests

2 participants