ttcn3-bts-test regressions

Hi all, I was planning to do this long time ago, but somehow kept leaving this for later. Today I revisited the state of ttcn3-bts-test, which shows quite a few regressions. I believe they need to be investigated and eventually fixed, so I created several tickets for tracking these regressions in Osmocom's Redmine: * OS#5951: TC_early_immediate_assignment, * OS#5952: TC_ho_physical_info, * OS#5953: TC_ms_pwr_ctrl_{constant,pf_ewma}, * OS#5954: TC_pcu_data_ind_lqual_cb, * OS#5955: TC_pcu_[ext_]rach_content, TC_pcu_ptcch, * OS#5956: TC_rsl_rf_resource_ind. The following tickets already existed prior to my checkup: * OS#4023: TC_pcu_oml_alert, * OS#5242: TC_ipa_crcx_ack_addr, * OS#5517: TC_tx_power_ramp_adm_state_change. So far this is all about non-hopping configuration: https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/lastCompl… The freq. hopping configuration exhibits slightly more red TCs: https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/lastCompl… 92% vs 84% passing TCs to be precise, but this is kinda expected because of the limitations we have in fake_trx: FAKE_* CTRL commands are applied to just one transceiver, not affecting others, which are also part of the Mobile Allocation. Mostly the meas related TCs are affected. The following TC groups are quite stable and mostly all green: https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/lastCompl… https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/lastCompl… https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/lastCompl… https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/lastCompl… The following two TC groups have never been stable/all green, AFAICT: https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/lastCompl… https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/lastCompl… We may want to create more tickets for those, maybe less granular (i.e. one ticket per group). I am not familiar with these two TC groups, so would be nice to get some input from those who write them. What would it take to get them fixed? Are there any tickets already? If could not find any, but I only did a quick search. Best regards, Vadim. -- - Vadim Yanitskiy <vyanitskiy at sysmocom.de> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Director: Harald Welte