From e8018967dec009469488818106e0526b03399724 Mon Sep 17 00:00:00 2001 From: Daniel Willmann Date: Tue, 21 Aug 2018 14:18:00 +0200 Subject: MSC_Tests: Reliably pass TC_cr_before_reset I was able to reproduce the sporadic cr_before_reset failures by running both osmo-{stp,msc}-master with --cpus 0.1. In that case the first test run would fail for me because no BSSMAP RESET ACK was seen. Sleeping some seconds before sending the messages will make sure all components are connected. Note: TC_cr_before_reset is the first test executed in control so this seems to be why it sometimes fails in jenkins. Change-Id: Id745470231950e0a284f8c231246d3719f7617cc --- msc/MSC_Tests.ttcn | 2 ++ 1 file changed, 2 insertions(+) diff --git a/msc/MSC_Tests.ttcn b/msc/MSC_Tests.ttcn index 42ad27c5..4bdbc1d0 100644 --- a/msc/MSC_Tests.ttcn +++ b/msc/MSC_Tests.ttcn @@ -1765,6 +1765,8 @@ testcase TC_cr_before_reset() runs on MTC_CT { f_bssap_start(g_bssap[0]); + f_sleep(3.0); + /* Make a blind connection attemt, to trigger the deadlock condition */ BSSAP_DIRECT.send(ts_BSSAP_CONNECT_req(g_bssap[0].sccp_addr_peer, g_bssap[0].sccp_addr_own, 1, omit)); -- cgit v1.2.3