fixeria has submitted this change. ( 
https://gerrit.osmocom.org/c/docker-playground/+/36462?usp=email )

Change subject: ttcn3-bts-test: fix start_config_oml(): do not start BSC
......................................................................

ttcn3-bts-test: fix start_config_oml(): do not start BSC

As the comment states, the BSC container is not needed for the OML
tests.  The testsuite itself "speaks" OML to the IUT in this case.

Change-Id: Iab44b9ed83e917475c9e2e86ad32b303b05b2ace
Fixes: aad045f5 "ttcn3-bts-test: add env var to not run all configs"
Fixes: OS#6421
---
M ttcn3-bts-test/jenkins.sh
1 file changed, 14 insertions(+), 2 deletions(-)

Approvals:
  Jenkins Builder: Verified
  pespin: Looks good to me, approved
  laforge: Looks good to me, but someone else must approve




diff --git a/ttcn3-bts-test/jenkins.sh b/ttcn3-bts-test/jenkins.sh
index ed4ae37..38e3760 100755
--- a/ttcn3-bts-test/jenkins.sh
+++ b/ttcn3-bts-test/jenkins.sh
@@ -187,7 +187,6 @@
        cp oml/osmo-bts.gen.cfg $VOL_BASE_DIR/bts/
        network_replace_subnet_in_configs

-       start_bsc
        start_bts trx 1
        start_fake_trx
        start_trxcon
@@ -197,7 +196,6 @@
        docker_kill_wait ${BUILD_TAG}-trxcon
        docker_kill_wait ${BUILD_TAG}-fake_trx
        docker_kill_wait ${BUILD_TAG}-bts
-       docker_kill_wait ${BUILD_TAG}-bsc
 }

 # Frequency hopping tests require different configuration files

--
To view, visit https://gerrit.osmocom.org/c/docker-playground/+/36462?usp=email
To unsubscribe, or for help writing mail filters, visit 
https://gerrit.osmocom.org/settings

Gerrit-Project: docker-playground
Gerrit-Branch: master
Gerrit-Change-Id: Iab44b9ed83e917475c9e2e86ad32b303b05b2ace
Gerrit-Change-Number: 36462
Gerrit-PatchSet: 1
Gerrit-Owner: fixeria <[email protected]>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <[email protected]>
Gerrit-Reviewer: laforge <[email protected]>
Gerrit-Reviewer: osmith <[email protected]>
Gerrit-Reviewer: pespin <[email protected]>
Gerrit-MessageType: merged

Reply via email to