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

memory directory is still under ~/.ros/memory even if $ROS_HOME is defined #51

Open
razr opened this issue Oct 11, 2021 · 2 comments
Open
Assignees
Labels
benchmarks bug Something isn't working

Comments

@razr
Copy link
Member

razr commented Oct 11, 2021

even if $ROS_HOME is defined

ubuntu@ubuntu:~/ros2$ echo $ROS_HOME
/home/ubuntu/ros2

after running colcon test --packages-select $(colcon list -n --base-paths src/reference-system/) the memory directory is under ~/.ros/memory

@flynneva
Copy link
Collaborator

@razr is the tracing directory at least properly created in the ROS_HOME directory? I'll look into this today.

@razr
Copy link
Member Author

razr commented Oct 11, 2021

yes, it is.

ubuntu@ubuntu:~/ros2$ ls tracing/
callback_autoware_default_multithreaded_rmw_cyclonedds_cpp_5s
callback_autoware_default_singlethreaded_rmw_cyclonedds_cpp_5s
callback_autoware_default_staticsinglethreaded_rmw_cyclonedds_cpp_5s

log directory for the tests is also under $ROS_HOME/log, however it looks like that it is overlapping with the log coming from the build. Not sure it is intended.

@flynneva flynneva self-assigned this Oct 23, 2021
@flynneva flynneva added the bug Something isn't working label Oct 23, 2021
@carlossvg carlossvg moved this to Todo in RTWG roadmap Apr 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
benchmarks bug Something isn't working
Projects
Status: Todo
Development

No branches or pull requests

3 participants