fixup BTS_Tests: verify hopping parameters in the INFO.ind message
Pass transceiver number to f_resolve_fh_params(), otherwise the hopping parameters would always be generated for TRX#0, and thus the expectations for TRX#N > 0 would be wrong. Change-Id: If1a25f5ff1b1bca900d54cc56e2045df5a81f4e2 Fixes: I9bb164fd2c7c48b91e0d7bd1abaf3cfec155342c Related: SYS#4868, OS#4547
This commit is contained in:
parent
aa553eda65
commit
7e1d0a23fe
|
@ -5422,7 +5422,7 @@ testcase TC_pcu_info_ind_fh_params() runs on test_CT {
|
|||
}
|
||||
|
||||
if (mp_freq_hop_enabled and mp_transceiver_num > 1)
|
||||
{ f_resolve_fh_params(fhp, tn); }
|
||||
{ f_resolve_fh_params(fhp, tn, trx_nr := i); }
|
||||
else
|
||||
{ fhp.enabled := false; }
|
||||
|
||||
|
|
Loading…
Reference in New Issue