summaryrefslogtreecommitdiffstats
path: root/ggsn_tests
diff options
context:
space:
mode:
authorStefan Sperling <ssperling@sysmocom.de>2018-07-26 17:57:08 +0200
committerHarald Welte <laforge@gnumonks.org>2018-07-27 07:40:10 +0000
commitcb111b21aba1d5881da1a1d3f19754cbd15b3779 (patch)
treede02d8eb9c8e4d31f107ff92ce6c7a530279bd5e /ggsn_tests
parentcd9e86f618299347a03595199f2260e6fbb7dc21 (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 'ggsn_tests')
-rw-r--r--ggsn_tests/GGSN_Tests.default1
1 files changed, 1 insertions, 0 deletions
diff --git a/ggsn_tests/GGSN_Tests.default b/ggsn_tests/GGSN_Tests.default
index ff0cd97..4d52e24 100644
--- a/ggsn_tests/GGSN_Tests.default
+++ b/ggsn_tests/GGSN_Tests.default
@@ -8,6 +8,7 @@
*.GGSNVTY.CTRL_DETECT_SERVER_DISCONNECTED := "yes"
*.GGSNVTY.CTRL_READMODE := "buffered"
*.GGSNVTY.CTRL_CLIENT_CLEANUP_LINEFEED := "yes"
+*.GGSNVTY.CTRL_DETECT_CONNECTION_ESTABLISHMENT_RESULT := "yes"
*.GGSNVTY.PROMPT1 := "OsmoGGSN> "
[MODULE_PARAMETERS]