You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I saw, that recently there was a bigger change regarding running tests with catkin_tools. I think this might be a regression because of this change. Maybe it is now intended to use these arguments in a different way, but the documentation doesn't say anything about it.
The text was updated successfully, but these errors were encountered:
I saw that in the PR #676 in fact the documentation has been updated. It looks like, that it did not propagate to catkin-tools.readthedocs.io, yet. The new documentation does not mention this arguments anymore. Maybe "--no-deps" is now default?
I found a workaround with intended behavior and similar (same?) output:
To replicate the old behavior, you can indeed use the command that you found. However, I would recommend to use the new catkin test verb that can be used like this: catkin test <any_package> --interleave-output. It runs the same tests as run_tests but has a more useful output. --no-deps became the default for catkin test. I added the --no-deps and --no-color arguments for backwards compatibility in #693, thank you for pointing out the regression.
System Info
I installed the most recent master branch with:
pip3 install -U "git+https://github.com/catkin/catkin_tools.git#egg=catkin_tools"
Expected Behavior
When running tests with catkin_tools, it should be able to find the arguments "--no-deps" and "--no-color".
Actual Behavior
When running the tests with catkin_tools, the arguments "--no-deps" and "--no-color" are not found anymore. I get following error message:
Steps to Reproduce the Issue
Just run following command with any package:
I saw, that recently there was a bigger change regarding running tests with catkin_tools. I think this might be a regression because of this change. Maybe it is now intended to use these arguments in a different way, but the documentation doesn't say anything about it.
The text was updated successfully, but these errors were encountered: