I had some troubles with test send actions : There I launch in the c++ code the rosEndEffectorExecutor (and not by hand in the terminal as we do usually). This gives an error about some std::map out of range, I do not know exactly where. The error is also visible at travis here
For now, I solved putting a sleep in the test after launching the node. On my pc 1 sec was enough, maybe on travis is too low (that the reason of the build fail). So, without sleeping, probably ROSEE does not have the time to do its initialization stuff.
I was wondering, instead of this ugly waiting, it is better to have a ROS service that, when called, return the status of ROSEndEffector main node? Or this uselessy puts more work and delays? @liesrock what do you think?
I had some troubles with test send actions : There I launch in the c++ code the rosEndEffectorExecutor (and not by hand in the terminal as we do usually). This gives an error about some std::map out of range, I do not know exactly where. The error is also visible at travis here
For now, I solved putting a sleep in the test after launching the node. On my pc 1 sec was enough, maybe on travis is too low (that the reason of the build fail). So, without sleeping, probably ROSEE does not have the time to do its initialization stuff.
I was wondering, instead of this ugly waiting, it is better to have a ROS service that, when called, return the status of ROSEndEffector main node? Or this uselessy puts more work and delays? @liesrock what do you think?