Started by an SCM change100078717ab2b75b4663722d4b5e720712b316c0a81078717ab2b75b4663722d4b5e720712b316c0a81refs/remotes/origin/master078717ab2b75b4663722d4b5e720712b316c0a81078717ab2b75b4663722d4b5e720712b316c0a81refs/remotes/origin/master078717ab2b75b4663722d4b5e720712b316c0a81078717ab2b75b4663722d4b5e720712b316c0a81refs/remotes/origin/mastergit://git.osmocom.org/docker-playgroundhttps://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/100/artifacthttps://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/changeshttps://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/100/https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/100/testReportfalse#100350255update-osmo-ci-on-slaves-dp #100100falsefalse100267572SUCCESS1600074877065https://jenkins.osmocom.org/jenkins/view/gerrit/job/update-osmo-ci-on-slaves-dp/100/admin2-deb9build- ttcn3-bts-test/fh/BTS_Tests.cfgttcn3-bts-test/fh/osmo-bsc.cfg078717ab2b75b4663722d4b5e720712b316c0a811599916591000https://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyvyanitskiy@sysmocom.dettcn3-bts-test/fh: do not configure CBCH slots statically
In BTS_Tests_SMSCB, we dynamically configure the CBCH slots via
the VTY interface, so there is no need to set them here. This
was also the reason of some SMSCB test case failures, because
the BSC would send unexpected LOAD INDICATIONs.
Change-Id: I6e005ca772e26878c7b19df0d854936d7b7718dd
Related: SYS#4868, OS#4708
2020-09-12 20:16:31 +0700078717ab2b75b4663722d4b5e720712b316c0a81ttcn3-bts-test/fh: do not configure CBCH slots staticallyeditttcn3-bts-test/fh/BTS_Tests.cfgeditttcn3-bts-test/fh/osmo-bsc.cfg
githttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyfixeria