In case you are debugging a failure of setting up a fixture using the yarpmanager, it is quite difficult to understand what is going on. This because the yarpmanager fixture manager does not print any information on which application it is launching, on which dependency is waiting, etc etc. It does not print anything even if the testrunner was launched with the verbose option.
This does make sense if using the yarpmanager application (because the user can check on the gui what is going on) but is a bit more complicated for use in rtf.
cc @apaikan What is a good strategy to add some (optional) verbose print to yarpmanager ? I saw that libYARP_manager is relativly yarp-indipendent, so I don't know it it make sense to use the yarp output macros in it.
In case you are debugging a failure of setting up a fixture using the yarpmanager, it is quite difficult to understand what is going on. This because the yarpmanager fixture manager does not print any information on which application it is launching, on which dependency is waiting, etc etc. It does not print anything even if the testrunner was launched with the
verboseoption.This does make sense if using the yarpmanager application (because the user can check on the gui what is going on) but is a bit more complicated for use in rtf.
cc @apaikan What is a good strategy to add some (optional) verbose print to yarpmanager ? I saw that
libYARP_manageris relativly yarp-indipendent, so I don't know it it make sense to use the yarp output macros in it.