Running a bundle's unit test suite generated a lot of warnings. The main offender is the warning that ruby tasks don't have a logger, which is now disabled by specifying that all deployments of a given process server should not be logged.
The second warning, of rebinding existing CORBA naming service entries, happens when running unit test suites in parallel, or - worse - when running a unit test suite while a system is running on the same machine. This is resolved by making registration optional. Note that to not get another warning in its place, one has to set ORO_NO_EMIT_CORBA_IOR while building RTT, like this:
setup_package "rtt" do |pkg|
pkg.define "ORO_NO_EMIT_CORBA_IOR", true
end
Depends on:
Running a bundle's unit test suite generated a lot of warnings. The main offender is the warning that ruby tasks don't have a logger, which is now disabled by specifying that all deployments of a given process server should not be logged.
The second warning, of rebinding existing CORBA naming service entries, happens when running unit test suites in parallel, or - worse - when running a unit test suite while a system is running on the same machine. This is resolved by making registration optional. Note that to not get another warning in its place, one has to set ORO_NO_EMIT_CORBA_IOR while building RTT, like this: