diff options
| author | Neels Hofmeyr <nhofmeyr@sysmocom.de> | 2023-04-25 02:31:51 +0200 |
|---|---|---|
| committer | Neels Hofmeyr <nhofmeyr@sysmocom.de> | 2023-04-25 02:34:46 +0200 |
| commit | 6549928fe019e5ae37efe033b3a4f04333a8e02a (patch) | |
| tree | bf16274d9faeb8d5150a139d4297b50dc2446aff | |
| parent | 545492d3e00200c359bbb3fec1a412f9e57d588b (diff) | |
hnbgw: wait longer for PFCP Assoc
Since I introduced stricter timeouts on PFCP messages in
hnbgw: add f_pfcp_expect()
commit 6bbfe057afe6f23e2f325789a3dcac81065ab952
Change-Id I2117475b695d486b1204d61e5bb21120a6187354
the HNBGW tests with PFCP support fail often:
The Assoc Setup resending timeout (X26) is configured to 5 seconds, and
the timeout to wait for this is also 5 seconds. Every once in a while
they happen to miss, causing a test failure.
Increase the initial Assoc Setup Req timeout to 15 seconds to avoid
sporadic failures.
Change-Id: I4b9af224e2346a4735f3d4e01b234acf56c5f3ff
| -rw-r--r-- | hnbgw/HNBGW_Tests.ttcn | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/hnbgw/HNBGW_Tests.ttcn b/hnbgw/HNBGW_Tests.ttcn index 1c0b121e..e9693fe6 100644 --- a/hnbgw/HNBGW_Tests.ttcn +++ b/hnbgw/HNBGW_Tests.ttcn @@ -1292,10 +1292,10 @@ template GtpParameters t_GtpParameters := { } } -private function f_pfcp_expect(template (present) PDU_PFCP exp_rx) runs on ConnHdlr return PDU_PFCP +private function f_pfcp_expect(template (present) PDU_PFCP exp_rx, float wait_time := 5.0) runs on ConnHdlr return PDU_PFCP { var PDU_PFCP rx; - timer T := 5.0; + timer T := wait_time; T.start; alt { [] PFCP.receive(exp_rx) -> value rx { @@ -1325,7 +1325,7 @@ friend function f_tc_ps_rab_assignment_with_pfcp(charstring id, TestHdlrParams p var PDU_PFCP m; var Node_ID upf_node_id := valueof(ts_PFCP_Node_ID_fqdn("\07osmocom\03org")); - m := f_pfcp_expect(tr_PFCP_Assoc_Setup_Req()) + m := f_pfcp_expect(tr_PFCP_Assoc_Setup_Req(), wait_time := 15.0); PFCP.send(ts_PFCP_Assoc_Setup_Resp(m.sequence_number, upf_node_id, ts_PFCP_Cause(REQUEST_ACCEPTED), 1234)); |