Fix mqueue transport and corba ipc tests #147
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a regression in the mqueue transport from a34a19a. The inputReady() call on the receiving side of the channel did not block anymore on the data sample being received and therefore the
corba_mqueue_ipc_test
can fail depending on the number of CPUs available and load.Furthermore I improved both tests that involve IPC, the
corba_ipc_test
andcorba_mqueue_ipc_test
to be more resilient against execution under high CPU load or on slow machines. Additionally, aresetCallBackPeer()
method has been introduced in order to allow multiple executions of the test (the client) against the same running server process.This PR will hopefully fix the test errors on Travis for the toolchain-2.9 branch.