From bf8c71f8ac382f9f50995775e5ba44ada5cec506 Mon Sep 17 00:00:00 2001 From: Pau Espin Pedrol Date: Tue, 20 Apr 2021 12:23:28 +0200 Subject: pcu: Fix TC_n3105_max_t3195 The previously request Dummy block was processed later in an unrelated place of the test, hence making expectations fail. The condition T_3195.running doesn't really change the logic/behavior, but removes an annoying warning in log files everytime the alt step is run. Change-Id: I4aa25d1220ccbeb8f1870f36651c9d6793a452b1 --- pcu/PCU_Tests.ttcn | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/pcu/PCU_Tests.ttcn b/pcu/PCU_Tests.ttcn index d4fe0042..e946d967 100644 --- a/pcu/PCU_Tests.ttcn +++ b/pcu/PCU_Tests.ttcn @@ -1746,9 +1746,13 @@ testcase TC_n3105_max_t3195() runs on RAW_PCU_Test_CT { block_nr := nr.blk_nr)); repeat; } - [] T_3195.timeout { + [T_3195.running] T_3195.timeout { log("T_3195 timeout"); - /* Done in alt */ + /* Done in alt, wait for pending RTS initiated previously in + * above case before continuing (expect /* Dummy block): */ + BTS.receive(tr_PCUIF_DATA_PDTCH(nr.bts_nr, + tr_PCUIF_DATA(nr.trx_nr, nr.ts_nr, sapi := PCU_IF_SAPI_PDTCH), + tr_RLCMAC_DUMMY_CTRL)); } [] BTS.receive { setverdict(fail, "Unexpected BTS message"); -- cgit v1.2.3