On Sun, Jun 25, 2017 at 6:22 AM, Neels Hofmeyr <nhofmeyr(a)sysmocom.de> wrote:
Tom mentioned the idea of running osmo-bts-trx on a
different machine from
osmo-trx -- that is certainly possible in a manual test, but I guess not really
an option for the regular tests. It would be a lot of manual supervision to
perform a series of tests, like 20 or more, to find out the success rate; or a
code and jenkins config change to run the osmo-bts-trx binary on a different
build slave, not trivial. It would be much preferred to stay on a single host
computer...
To be clear, I am not advocating the use of a separate machines as a
permanent solution, which I agree is not ideal, but as a method to
confirm that the issue is directly related to process scheduling.
-TT