Actions
Bug #6421
closedBTS_Tests_OML.* all started to fail for latest+master
Start date:
03/26/2024
Due date:
% Done:
100%
Spec Reference:
Description
- https://jenkins.osmocom.org/jenkins/view/All%20no%20Gerrit/job/ttcn3-bts-test-latest/test_results_analyzer/
- https://jenkins.osmocom.org/jenkins/view/All%20no%20Gerrit/job/ttcn3-bts-test/test_results_analyzer/
Given that both master and latest are failing, I presume it's a bug in our testsuite and not a regression in the actual software
In case anyone knows what might have caused this, please report here ASAP and'or adopt the ticket. Thanks!
Updated by fixeria about 1 month ago
- Status changed from New to In Progress
- Assignee changed from osmith to fixeria
I think I found the problem:
181 # OML tests require us to run without BSC
182 start_config_oml() {
183 if ! test_config_enabled "oml"; then
184 return
185 fi
186
187 cp oml/osmo-bts.gen.cfg $VOL_BASE_DIR/bts/
188 network_replace_subnet_in_configs
189
190 start_bsc # <-----------------------
191 start_bts trx 1
192 start_fake_trx
193 start_trxcon
194
195 start_testsuite oml
We should not be staring the BSC container, as the comment suggests.
Updated by fixeria about 1 month ago
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
Here is a patch:
https://gerrit.osmocom.org/c/docker-playground/+/36462 ttcn3-bts-test: fix start_config_oml(): do not start BSC [NEW]
I gave it a try on the build machine and the OML tests are passing with it.
Updated by fixeria about 1 month ago
- Status changed from Feedback to Resolved
https://jenkins.osmocom.org/jenkins/view/TTCN3/job/ttcn3-bts-test/2348/ -- Test Result (46 failures / -15)
Actions