Skip to content
Success

Changes

Summary

  1. ttcn3-bts: Fix most OML test failing after osmo-bts shutdown (details)
Commit fc5cab9e3a3c5ac9edcd0a5c78c43c5221c16883 by Pau Espin Pedrol
ttcn3-bts: Fix most OML test failing after osmo-bts shutdown optimization

Since osmo-bts.git 0a6bdb024f5429a35c56178496158c9b1c3ee032, the process
is quickly terminated during shutdown if no TRX is running. Since in the
OML tests the TTCN3 components implements the OML IPA server side, most
of the time when osmo-bts starts it finds no one listening on the
address and exits immediately. This makes respawn.sh script run osmo-bts
lots of times per seconds (since osmo-bts terminates quicker now). As a
result, it quickly consumes the 500 launch threshold and exits without
starting osmo-bts being launched anymore.
As a result, only first tests pass, and all the later ones fail because
osmo-bts never connects.

Let's add a sleep 1 between respawns in respawn.sh only when running OML
tests (not needed in the others since there's an osmo-bsc always
running). This also clears a lot of output in the logs of osmo-bts
processes restarting over and over again.

Change-Id: I10d3e1ef8325dd78f9ae2b95fbfd1c6d893bf8a4
The file was modifiedosmo-bts-master/respawn.sh
The file was modifiedttcn3-bts-test/jenkins.sh