diff options
| author | Stefan Sperling <ssperling@sysmocom.de> | 2018-07-26 17:57:08 +0200 |
|---|---|---|
| committer | Harald Welte <laforge@gnumonks.org> | 2018-07-27 07:40:10 +0000 |
| commit | cb111b21aba1d5881da1a1d3f19754cbd15b3779 (patch) | |
| tree | de02d8eb9c8e4d31f107ff92ce6c7a530279bd5e /bsc/BSC_Tests.default | |
| parent | cd9e86f618299347a03595199f2260e6fbb7dc21 (diff) | |
detect VTY TELNET port connection failures in TTCN3 tests
Pass the CTRL_DETECT_CONNECTION_ESTABLISHMENT_RESULT parameter to
the TELNET port by default. This allows tests to make progress
into an error handling path if they are started while the osmo-*
program they want to connect on VTY is not running.
Observed with osmo-ggsn tests, where if the one test runs
into a VTY connection failure the subsequent test would get
stuck forever in a map() call on the VTY TELNET port.
Change-Id: I9acf7793d5d68aec6d087cff254a10d8b673dab1
Related: OS#3149
Diffstat (limited to 'bsc/BSC_Tests.default')
| -rw-r--r-- | bsc/BSC_Tests.default | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/bsc/BSC_Tests.default b/bsc/BSC_Tests.default index c13f7b03..88183591 100644 --- a/bsc/BSC_Tests.default +++ b/bsc/BSC_Tests.default @@ -15,6 +15,7 @@ mtc.FileMask := LOG_ALL | TTCN_DEBUG | TTCN_MATCHING | DEBUG_ENCDEC; *.BSCVTY.CTRL_DETECT_SERVER_DISCONNECTED := "yes" *.BSCVTY.CTRL_READMODE := "buffered" *.BSCVTY.CTRL_CLIENT_CLEANUP_LINEFEED := "yes" +*.BSCVTY.CTRL_DETECT_CONNECTION_ESTABLISHMENT_RESULT := "yes" *.BSCVTY.PROMPT1 := "OsmoBSC> " [MODULE_PARAMETERS] |