Started by timerOSMO_GSM_TESTER_BRANCHorigin/masterOSMO_GSM_TESTER_OPTS-T25902be32ea554735da9f2ba9e39f2594fbc2284639b2be32ea554735da9f2ba9e39f2594fbc2284639brefs/remotes/origin/pespin/ttcn32be32ea554735da9f2ba9e39f2594fbc2284639b2be32ea554735da9f2ba9e39f2594fbc2284639brefs/remotes/origin/pespin/ttcn327627aa14e45f455f87c1dfe9966d759093af9f6d6fc7aa14e45f455f87c1dfe9966d759093af9f6d6fcrefs/remotes/origin/master7aa14e45f455f87c1dfe9966d759093af9f6d6fc7aa14e45f455f87c1dfe9966d759093af9f6d6fcrefs/remotes/origin/master7aa14e45f455f87c1dfe9966d759093af9f6d6fc7aa14e45f455f87c1dfe9966d759093af9f6d6fcrefs/remotes/origin/mastergit://git.osmocom.org/osmo-gsm-tester303testReporttrial-2762-bin.tgztrial-2762-bin.tgztrial-2762-bin.tgztrial-2762-run.tgztrial-2762-run.tgztrial-2762-run.tgzfalse#276243944013713736osmo-gsm-tester_ttcn3 #27622762falsefalse2762409782FAILURE1614554340522https://jenkins.osmocom.org/jenkins/job/osmo-gsm-tester_ttcn3/2762/osmo-gsm-tester-prod- sysmocom/scenarios/mod-enb-cells-interenb-ho.confe8ab10cb2262b407406053bc3dd6b2adf1cee4d71605169416000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comenb: add scenario file for inter-eNB HO with two cells
Change-Id: I356a81814a2d7714a1a5252aa357257901fa6227
2020-11-12 09:23:36 +0100e8ab10cb2262b407406053bc3dd6b2adf1cee4d7enb: add scenario file for inter-eNB HO with two cellsaddsysmocom/scenarios/mod-enb-cells-interenb-ho.conf
- sysmocom/scenarios/mod-enb-cells-intra-freq-ho.confsysmocom/scenarios/mod-enb-cells-intraenb-intrafreq-ho.confsysmocom/scenarios/mod-enb-cells-inter-freq-ho.conf76021babc7353f87d4251345bd44d4a42e8abac31605869443000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comcell_modifiers: refactor HO cell configs
* rename intrafreq vs intraenb
* add missing mandatory params
Change-Id: Icc1fe5c1711ecbed2f1b8b1e6a0b51c2d28ec651
2020-11-20 11:50:43 +010076021babc7353f87d4251345bd44d4a42e8abac3cell_modifiers: refactor HO cell configsdeletesysmocom/scenarios/mod-enb-cells-intra-freq-ho.confaddsysmocom/scenarios/mod-enb-cells-intraenb-intrafreq-ho.confdeletesysmocom/scenarios/mod-enb-cells-inter-freq-ho.conf
- src/osmo_gsm_tester/obj/enb_srs.pysrc/osmo_gsm_tester/templates/srsue.conf.tmplsrc/osmo_gsm_tester/core/schema.pysysmocom/scenarios/cfg-enb-enable-ul-qam64.confsrc/osmo_gsm_tester/templates/srsenb_sib.conf.tmpl3166b6353e7e2c5eff29730f4a08184118825d911605869443000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comenb: add QAM64 support for UL
* add new UE feature
* enable in srsue.conf.templ
* add new table for maximum rates
* add config scenario to enable SIB option for QAM64
Change-Id: I6ac2c9989a761e91b93d76c2507f55f0140b202d
2020-11-20 11:50:43 +01003166b6353e7e2c5eff29730f4a08184118825d91enb: add QAM64 support for ULeditsrc/osmo_gsm_tester/core/schema.pyeditsrc/osmo_gsm_tester/obj/enb_srs.pyaddsysmocom/scenarios/cfg-enb-enable-ul-qam64.confeditsrc/osmo_gsm_tester/templates/srsue.conf.tmpleditsrc/osmo_gsm_tester/templates/srsenb_sib.conf.tmpl
- sysmocom/scenarios/mod-2enb-nprb@.conf25bc1e07e45bb6e5ed2048ce0da4f1637f38144e1605873787000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comadd scenario to modify bandwith of 2 eNB objects
required for Inter-eNB HO configs, for example.
Change-Id: Iaf053941ff31c4ba94edf67fc54c0f1c1441577d
2020-11-20 13:03:07 +010025bc1e07e45bb6e5ed2048ce0da4f1637f38144eadd scenario to modify bandwith of 2 eNB objectsaddsysmocom/scenarios/mod-2enb-nprb@.conf
- src/osmo_gsm_tester/obj/ms_amarisoft.pysrc/osmo_gsm_tester/templates/amarisoft_lteue.cfg.tmplsysmocom/defaults.confsysmocom/scenarios/cfg-ms-count@.confsrc/osmo_gsm_tester/obj/ms.py65a9e741ad489abcb69b146e500f13706a5a45351606131232000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comms_amarisoft: fix various regressions
this patch fixes some regressions in the Amarisoft UE class,
the config template, etc. that have been undetected bc we never
executed tests with it.
Change-Id: I397e675a4018acf3372a3b7e29fd864703b2b919
2020-11-23 12:33:52 +010065a9e741ad489abcb69b146e500f13706a5a4535ms_amarisoft: fix various regressionseditsrc/osmo_gsm_tester/obj/ms_amarisoft.pyeditsysmocom/defaults.confaddsysmocom/scenarios/cfg-ms-count@.confeditsrc/osmo_gsm_tester/obj/ms.pyeditsrc/osmo_gsm_tester/templates/amarisoft_lteue.cfg.tmpl
- contrib/jenkins-build-amarisoft.sha07af115fef4cdf25a9d57bfe8f2576457b8f2321606742830000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comjenkins-build-amarisoft.sh: set symlink to srslte_rf lib
Change-Id: Ifc8e5ba0dd59fb92cdf22f2a18acea904e2153f7
2020-11-30 14:27:10 +0100a07af115fef4cdf25a9d57bfe8f2576457b8f232jenkins-build-amarisoft.sh: set symlink to srslte_rf libeditcontrib/jenkins-build-amarisoft.sh
- src/osmo_gsm_tester/external/gnuradio_zmq_broker_remote.pyb33f36b9fb68c93135ed063e7b389203548e57641606742830000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comgnuradio_zmq_broker_remote: fix eNB port mapping for carrier aggregation
the mapping of ports didn't consider when a eNB had two ports for
different EARFCNs
Change-Id: I5548f67a3b37b03482e4b6172828fcd891e704a5
2020-11-30 14:27:10 +0100b33f36b9fb68c93135ed063e7b389203548e5764gnuradio_zmq_broker_remote: fix eNB port mapping for carrier aggregationeditsrc/osmo_gsm_tester/external/gnuradio_zmq_broker_remote.py
- src/osmo_gsm_tester/obj/run_node.pysrc/osmo_gsm_tester/core/remote.pysrc/osmo_gsm_tester/core/process.py2af2b15e2e7105581d21734d351653f70c6863d11606753971000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@sysmocom.deProcess: Add remote_port as new parameter
remote_port defines a custom/additional port for
connections over ssh. It may be used in case several
ssh instances share one IP address.
Change-Id: I2c93fd2ea1c10c333d00eafd3c1066c35796e398
2020-11-30 16:32:51 +00002af2b15e2e7105581d21734d351653f70c6863d1Process: Add remote_port as new parametereditsrc/osmo_gsm_tester/obj/run_node.pyeditsrc/osmo_gsm_tester/core/remote.pyeditsrc/osmo_gsm_tester/core/process.py
- sysmocom/resources.conf.prod2bd357cf021d4fa49ba5dedc90c314e3ffa8ed941606953731000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.deprod: after hardware move, adjust modem pci for sierra_1st and sierra_2nd (ONLY TWO)
Doing only the first two modems so far because I need them for handover
runs. The other modems are still todo!
Change-Id: Ibd71acfc76c01ffd105abe5effc1d246b1e65f85
2020-12-03 01:02:11 +01002bd357cf021d4fa49ba5dedc90c314e3ffa8ed94prod: after hardware move, adjust modem pci for sierra_1st and sierra_2nd (ONLY TWO)editsysmocom/resources.conf.prod
- contrib/jenkins-build-osmo-pcu-sysmo.shcontrib/jenkins-build-osmo-pcu-oc2g.sh92ebea1dc113298c7aea126e64e8e6795ab9f3c11607344997000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@espeweb.netcontrib: Disable libmnl dependency cross-compiling osmo-pcu
Only newest OE SDKs have libmnl added, but we don't need this feature
anyway, so let's disable it in order to get builds running fine again.
Change-Id: Id3b30d0b183cd21fd6df89fdda5581ab58c7a9a5
2020-12-07 13:43:17 +010092ebea1dc113298c7aea126e64e8e6795ab9f3c1contrib: Disable libmnl dependency cross-compiling osmo-pcueditcontrib/jenkins-build-osmo-pcu-oc2g.sheditcontrib/jenkins-build-osmo-pcu-sysmo.sh
- contrib/jenkins-build-osmo-bts-oc2g.shcontrib/jenkins-build-osmo-bts-sysmo.sh8d27b184808188124c780e31ed26ce21b2e11f021607425327000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@espeweb.netcontrib: Disable libmnl dependency cross-compiling osmo-bts
Only newest OE SDKs have libmnl added, but we don't need this feature
anyway, so let's disable it in order to get builds running fine again.
Change-Id: Ief9cbca6e10b1ed6acf6e079f660fc3f7c863c7b
2020-12-08 12:02:07 +01008d27b184808188124c780e31ed26ce21b2e11f02contrib: Disable libmnl dependency cross-compiling osmo-btseditcontrib/jenkins-build-osmo-bts-oc2g.sheditcontrib/jenkins-build-osmo-bts-sysmo.sh
- selftest/suite_test/suite_test.oksrc/osmo_gsm_tester/templates/osmo-trx.cfg.tmplsrc/osmo_gsm_tester/templates/osmo-bts-virtual.cfg.tmplsrc/osmo_gsm_tester/templates/osmo-mgcpgw.cfg.tmplsrc/osmo_gsm_tester/templates/osmo-sgsn.cfg.tmplsrc/osmo_gsm_tester/templates/osmo-bts-oc2g.cfg.tmplsrc/osmo_gsm_tester/templates/osmo-stp.cfg.tmplsrc/osmo_gsm_tester/templates/osmo-bts-trx.cfg.tmplsrc/osmo_gsm_tester/templates/osmo-bsc.cfg.tmplsrc/osmo_gsm_tester/templates/osmo-pcu-sysmo.cfg.tmplsrc/osmo_gsm_tester/templates/osmo-bts-octphy.cfg.tmplsrc/osmo_gsm_tester/templates/osmo-pcu.cfg.tmplsrc/osmo_gsm_tester/templates/osmo-bts-sysmo.cfg.tmplsrc/osmo_gsm_tester/templates/osmo-pcu-oc2g.cfg.tmplsrc/osmo_gsm_tester/templates/osmo-hlr.cfg.tmplsrc/osmo_gsm_tester/templates/osmo-ggsn.cfg.tmplsrc/osmo_gsm_tester/templates/osmo-msc.cfg.tmplb5a3d6732a04e149c7acba6b277d41c41f55e6621607641407000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrnhofmeyr@sysmocom.decfg templates: log level and source basename last, log no category-hex
Makes for saner log output in stderr files.
Change-Id: I2755beffd18d6779367c04e4aaaed119d66eb3be
2020-12-10 23:03:27 +0000b5a3d6732a04e149c7acba6b277d41c41f55e662cfg templates: log level and source basename last, log no category-hexeditsrc/osmo_gsm_tester/templates/osmo-hlr.cfg.tmpleditsrc/osmo_gsm_tester/templates/osmo-msc.cfg.tmpleditsrc/osmo_gsm_tester/templates/osmo-sgsn.cfg.tmpleditsrc/osmo_gsm_tester/templates/osmo-mgcpgw.cfg.tmpleditselftest/suite_test/suite_test.okeditsrc/osmo_gsm_tester/templates/osmo-bts-sysmo.cfg.tmpleditsrc/osmo_gsm_tester/templates/osmo-pcu-sysmo.cfg.tmpleditsrc/osmo_gsm_tester/templates/osmo-bts-virtual.cfg.tmpleditsrc/osmo_gsm_tester/templates/osmo-trx.cfg.tmpleditsrc/osmo_gsm_tester/templates/osmo-pcu.cfg.tmpleditsrc/osmo_gsm_tester/templates/osmo-bts-trx.cfg.tmpleditsrc/osmo_gsm_tester/templates/osmo-pcu-oc2g.cfg.tmpleditsrc/osmo_gsm_tester/templates/osmo-bts-octphy.cfg.tmpleditsrc/osmo_gsm_tester/templates/osmo-ggsn.cfg.tmpleditsrc/osmo_gsm_tester/templates/osmo-bts-oc2g.cfg.tmpleditsrc/osmo_gsm_tester/templates/osmo-bsc.cfg.tmpleditsrc/osmo_gsm_tester/templates/osmo-stp.cfg.tmpl
- src/osmo_gsm_tester/obj/osmo_vty.py106865a75f60f0586dcd85363efa8e14acc4c37f1607642353000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.deadd osmo_vty.py
To trigger manual handovers, I need a VTY interface. The non-trivial
parts of this are copied from osmo-python-tests osmo_interact_vty.py.
Will be used in the upcoming handover_2G test suite in
I0b2671304165a1aaae2b386af46fbd8b098e3bd8.
Change-Id: I7c17b143b7c690b8c4105ee7c6272670046fa91d
2020-12-11 00:19:13 +0100106865a75f60f0586dcd85363efa8e14acc4c37fadd osmo_vty.pyaddsrc/osmo_gsm_tester/obj/osmo_vty.py
- src/osmo_gsm_tester/testenv.pysrc/osmo_gsm_tester/obj/osmo_vty.pysrc/osmo_gsm_tester/obj/bsc_osmo.pyaf4e2317dc904a31f4ec756c63d2a16830a72d3d1607642353000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.deadd bsc.vty: always keep a BSC VTY connection ready
The BSC's VTY port will be used to trigger manual handover, and to
retrieve a list of active lchans from the BSC, in the upcoming
handover_2G test suite, I0b2671304165a1aaae2b386af46fbd8b098e3bd8.
Change-Id: I06652db04fc9e48748f3c2196334f5352e9cc48a
2020-12-11 00:19:13 +0100af4e2317dc904a31f4ec756c63d2a16830a72d3dadd bsc.vty: always keep a BSC VTY connection readyeditsrc/osmo_gsm_tester/testenv.pyeditsrc/osmo_gsm_tester/obj/bsc_osmo.pyeditsrc/osmo_gsm_tester/obj/osmo_vty.py
- src/osmo_gsm_tester/obj/bsc_osmo.pyca155b6c37e16cdcdfd8fa95c4f2ada30b0b32701607642353000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.debsc: add active lchan matching via vty
Will be used in upcoming handover_2G test suite in
I0b2671304165a1aaae2b386af46fbd8b098e3bd8, which needs to verify that a
handover actually ended up on the expected lchan.
Change-Id: I03df8f3ae2ee47930eee311c7ce104c36dbb3154
2020-12-11 00:19:13 +0100ca155b6c37e16cdcdfd8fa95c4f2ada30b0b3270bsc: add active lchan matching via vtyeditsrc/osmo_gsm_tester/obj/bsc_osmo.py
- src/osmo_gsm_tester/obj/bts.pyaa67f950273195c723d982ec2ce07e9f62b0f7811607642353000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.debts: allow configuring ARFCN and BSIC: add to schema
resources.conf is already allowed to set these, but in order to let
scenarios and suites modify these values, they need to be in the schema.
Change-Id: I8e0583e9208d563c66b0bdc9f25b1b74f92403c2
2020-12-11 00:19:13 +0100aa67f950273195c723d982ec2ce07e9f62b0f781bts: allow configuring ARFCN and BSIC: add to schemaeditsrc/osmo_gsm_tester/obj/bts.py
- src/osmo_gsm_tester/core/report.py7d79ea4d2a4f755850054149af6feb21303fca6c1607642353000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.delog passed tests
In the end of a test suite, do not omit the passed tests. For example,
running handover against N BTS combinations, it was hard to summarize
which BTS models actually succeeded, with only the failures listed.
Besides the "FAIL" listings, now print something like this in the end:
PASS: handover:sysmo+secondbts-trx-b200 (pass: 1)
pass: handover.py (198.8 sec)
PASS: handover:sysmo+secondbts-trx-umtrx (pass: 1)
pass: handover.py (192.7 sec)
PASS: handover:trx-b200+secondbts-trx-umtrx (pass: 1)
pass: handover.py (193.1 sec)
Change-Id: Ib85a5b90e267c2ed2f844691187ecadc8939b1bb
2020-12-11 00:19:13 +01007d79ea4d2a4f755850054149af6feb21303fca6clog passed testseditsrc/osmo_gsm_tester/core/report.py
- src/osmo_gsm_tester/core/resource.pysrc/osmo_gsm_tester/core/suite.pyselftest/suite_test/suite_test.okf07114f9e2637cc10e5db664c3c6199e9a8d62331607642353000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.delog reserved resources
On non-debug log level, show something like this at the beginning of
each suite:
03:45:49.439720 tst handover:sysmo+secondbts-trx-b200: RESERVED RESOURCES for handover:
bts
sysmoBTS 1002
Ettus B200
ip_address
10.42.42.2
10.42.42.3
10.42.42.4
10.42.42.5
10.42.42.6
10.42.42.7
modem
sierra_1st
sierra_2nd
Change-Id: Ic23556eafee654c93d13c5ef405028da09bd51d7
2020-12-11 00:19:13 +0100f07114f9e2637cc10e5db664c3c6199e9a8d6233log reserved resourceseditsrc/osmo_gsm_tester/core/resource.pyeditsrc/osmo_gsm_tester/core/suite.pyeditselftest/suite_test/suite_test.ok
- selftest/resource_test/resource_test.oksysmocom/defaults.confsysmocom/resources.conf.prodselftest/resource_test/resource_test.pysysmocom/resources.conf.rndsrc/osmo_gsm_tester/obj/bts_oc2g.pysrc/osmo_gsm_tester/core/schema.pysrc/osmo_gsm_tester/obj/bts_nanobts.pyselftest/resource_test/conf/resources.confselftest/suite_test/resources.confecce402f43b708bf178d603e2bd8587e72fdb3b11607642353000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.deconfigure fixed ARFCN per bts
Remove ARFCNs as a concept from resource pool, assign a fixed ARFCN to
each BTS and TRX in the resource pools.
Using ARFCNs on specific bands as resources was an idea that is hard to
implement, because specific BTS dictate selection of bands which
influences which ARFCNs can be picked. That means reserving ARFCN
resources is only possible after reserving specific BTS resources, but
the tester is currently not capable of such two-stage resolution.
Writing handover tests, I got the problem that both BTS in a scenario
attempt to use the same ARFCN.
The by far easiest solution is to assign one fixed ARFCN to each BTS and
TRX. If ever needed, a scenario modifier can still configure different
ARFCNs.
(Due to uncertainty about OC2G operation stability, I prefer to leave
OC2G on ARFCN 50, as it happened to end up being configured before this
patch.)
Change-Id: I0a6c60544226f4261f9106013478d6a27fc39f38
2020-12-11 00:19:13 +0100ecce402f43b708bf178d603e2bd8587e72fdb3b1configure fixed ARFCN per btseditselftest/suite_test/resources.confeditsysmocom/defaults.confeditsrc/osmo_gsm_tester/obj/bts_nanobts.pyeditsysmocom/resources.conf.prodeditsrc/osmo_gsm_tester/obj/bts_oc2g.pyeditselftest/resource_test/resource_test.okeditselftest/resource_test/conf/resources.confeditselftest/resource_test/resource_test.pyeditsrc/osmo_gsm_tester/core/schema.pyeditsysmocom/resources.conf.rnd
- src/osmo_gsm_tester/core/process.pyfc38393f8278d0ca6db904be142efaa91af7cca31607642353000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.deprocess: add get_output_mark() and grep_output()
Allow showing log lines matching specific regexes, from a specific start
point of a log.
My use case is to echo the handover related logging after an expected
handover failed, so that the reason is visible already in the console
output of a jenkins run. So far I would need to open the endless bsc log
and look up the matching place in it to get a conclusion about why a
handover failed.
Change-Id: Ib6569f7486e9d961bd79a5f24232e58d053667a1
2020-12-11 00:19:13 +0100fc38393f8278d0ca6db904be142efaa91af7cca3process: add get_output_mark() and grep_output()editsrc/osmo_gsm_tester/core/process.py
- selftest/suite_test/suite_test.oksrc/osmo_gsm_tester/core/log.pysrc/osmo_gsm_tester/core/test.py081e89f477d3a0209d1dddb652040c43b2b0b6ca1607642353000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.defix: line nr in test name in wrong places
test.Test() overrides name() in order to provide source line number
information. However, overriding name() is the wrong place for that, as
name() is also often used for identifying an object - when listing the
tests of a suite, the line number should not appear in the test name.
For example, the line number sometimes ends up in the test results in
jenkins, making 'foo.py' and 'foo.py:23' two distinct report items.
Instead, add a separate function Origin.src() that defaults to name(),
but specific classes can override src() if they wish to provide more
detailed information with the object name.
Override src() in Test, not name().
Use src() in backtraces.
The suite_test.ok shows that the backtracing in the log remains
unchanged, but the place where the test name is printed is corrected:
I am 'test_suite' / 'hello_world.py:23'
becomes
I am 'test_suite' / 'hello_world.py'
(Notice that "[LINENR]" in suite_test.ok is a masking of an actual
number, done within the selftest suite)
Change-Id: I0c4698fa2b3db3de777d8b6dcdcee84e433c62b7
2020-12-11 00:19:13 +0100081e89f477d3a0209d1dddb652040c43b2b0b6cafix: line nr in test name in wrong placeseditsrc/osmo_gsm_tester/core/log.pyeditselftest/suite_test/suite_test.okeditsrc/osmo_gsm_tester/core/test.py
- selftest/suite_test/suite_test.okselftest/suite_test/suitedirB/suiteC/test_template_overlay.pyselftest/template_test/template_test.pyselftest/template_test/template_test.ok112da03e98048374020ef2a41f9bb6f77f1ad4471607642353000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.detypo / newline in selftest log output
...because it otherwise causes confusing selftest log changes in
upcoming I0972c66b9165bd7f2b0b387e0335172849199193
Change-Id: I1eec31c5baba5ef33d0c8441b1e94a00d79af9bf
2020-12-11 00:19:13 +0100112da03e98048374020ef2a41f9bb6f77f1ad447typo / newline in selftest log outputeditselftest/template_test/template_test.okeditselftest/suite_test/suitedirB/suiteC/test_template_overlay.pyeditselftest/suite_test/suite_test.okeditselftest/template_test/template_test.py
- selftest/suite_test/suite_test.oksrc/osmo_gsm_tester/testenv.pysrc/osmo_gsm_tester/core/log.pysrc/osmo_gsm_tester/core/test.py3b493f35678a574a06dfbece61a2deda1bcc73ad1607642353000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.dedo not redirect_stdout in test scripts
In a test, I called print() on a multi-line string and saw the log
showing each line 0.2 seconds apart. redirect.stdout seems to be pretty
inefficient.
Instead, put a print() function into the testenv, to directly call log()
on the strings passed to print().
The initial idea for redirect_stdout was that we could print() in any
deeper functions called from a test script. But we have no such nested
print() anywhere, only in test scripts themselves.
As a result of this, a multi-line print() in test scripts now no longer
puts the log prefix (timestamp, test name...) and suffix (backtrace /
source position) to each single line, but prints the multiline block
between a single log prefix and suffix -- exactly like the log()
function does everywhere else.
I actually briefly implemented adding the log prefix to each separate
line everywhere, but decided that it is not a good idea: in some places
we log config file snippets and other lists, and prepending the log
prefix to each line makes pasting such a snippet from (say) a jenkins
log super cumbersome. And the log prefix (backtrace) attached on each
separate line makes multiline blocks very noisy, unreadable.
Change-Id: I0972c66b9165bd7f2b0b387e0335172849199193
2020-12-11 00:19:13 +01003b493f35678a574a06dfbece61a2deda1bcc73addo not redirect_stdout in test scriptseditsrc/osmo_gsm_tester/core/log.pyeditselftest/suite_test/suite_test.okeditsrc/osmo_gsm_tester/core/test.pyeditsrc/osmo_gsm_tester/testenv.py
- src/osmo_gsm_tester/core/process.pye5e5df8d24041d4c99705067d042d402d8f47c231607642353000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.delog: process.py: fix weird space in stdout/stderr log output
Log output before:
stdout:
| line1
| line2
| line3
After:
stdout:
| line1
| line2
| line3
Change-Id: I4202e7dfbb550acaf55a6c6487fc07819ab18b94
2020-12-11 00:19:13 +0100e5e5df8d24041d4c99705067d042d402d8f47c23log: process.py: fix weird space in stdout/stderr log outputeditsrc/osmo_gsm_tester/core/process.py
- src/osmo_gsm_tester/core/log.pysrc/osmo_gsm_tester/core/test.py12ed99628cf1c5b3bb91e948cb290bc5f27bad981607642353000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.deimplement test.get_log_output()
Retrieve a test's own logging. The aim is to provide logging belonging
to a given report fragment in the junit XML output, will be used by
upcoming test.report_fragment() feature.
Change-Id: Idfa0a45f3e6a18dd4fe692e81d732c70b5cffb76
2020-12-11 00:19:13 +010012ed99628cf1c5b3bb91e948cb290bc5f27bad98implement test.get_log_output()editsrc/osmo_gsm_tester/core/log.pyeditsrc/osmo_gsm_tester/core/test.py
- selftest/suite_test/suite_test.oksrc/osmo_gsm_tester/core/test.pyselftest/suite_test/suitedirA/test_suite/test_report_fragment.pyselftest/suite_test/suite_test.ok.ignselftest/suite_test/suite_test.pysrc/osmo_gsm_tester/core/report.py9596b210c5f1d7601d8939ed71e5e18ccde4c6521607642353000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.deadd test.report_fragment()
Allow enriching the junit output with arbitrary subtasks within a test.
The current aim is, for handover tests, to not just show that a test
failed, but to show exactly which steps worked and which didn't, e.g.:
handover.py/01_bts0_started PASSED
handover.py/02.1_ms0_attach PASSED
handover.py/02.2_ms1_attach PASSED
handover.py/02.3_subscribed_in_msc PASSED
handover.py/03_call_established PASSED
handover.py/04.1_bts1_started FAILED
In this case it is immediately obvious from looking at the jenkins
results analyzer that bts1 is the cause of the test failure, and it is
visible which parts of the test are flaky, over time.
First user Will be the upcoming handover_2G suite, in
I0b2671304165a1aaae2b386af46fbd8b098e3bd8.
Change-Id: I4ca9100b6f8db24d1f7e0a09b3b7ba88b8ae3b59
2020-12-11 00:19:13 +01009596b210c5f1d7601d8939ed71e5e18ccde4c652add test.report_fragment()addselftest/suite_test/suitedirA/test_suite/test_report_fragment.pyeditselftest/suite_test/suite_test.okeditselftest/suite_test/suite_test.ok.igneditsrc/osmo_gsm_tester/core/test.pyeditselftest/suite_test/suite_test.pyeditsrc/osmo_gsm_tester/core/report.py
- src/osmo_gsm_tester/core/log.pysrc/osmo_gsm_tester/core/report.py16c8be41c97e5fa7395ca9d83a7562c162e456d11607642353000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.dereport fragment: strip ansi colors from junit XML
Jenkins does support showing ANSI colors on the web, but apparently not
in the junit results output. Strip ansi colors from report fragment
<system-out> text, to make it less annoying to read those on jenkins.
Change-Id: I656ecc23bbfd3f25bdf012c890e0c998168844d3
2020-12-11 00:19:13 +010016c8be41c97e5fa7395ca9d83a7562c162e456d1report fragment: strip ansi colors from junit XMLeditsrc/osmo_gsm_tester/core/report.pyeditsrc/osmo_gsm_tester/core/log.py
- src/osmo_gsm_tester/obj/osmo_ctrl.py05439d70296533e79cfe23e7136e4e7a636bc2331607642353000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.dectrl: set socket timeout
The blocking CTRL socket must have a timeout.
So far we have always been reading from the CTRL socket in a blocking
way. So far we are always lucky that we are indeed getting a response to
receive. Should the CTRL interface ever fail to answer, the tester would
be stuck infinitely.
Change-Id: I20091daf13981dc3d0d894af5a65c23f4db0471d
2020-12-11 00:19:13 +010005439d70296533e79cfe23e7136e4e7a636bc233ctrl: set socket timeouteditsrc/osmo_gsm_tester/obj/osmo_ctrl.py
- src/osmo_gsm_tester/obj/osmo_ctrl.pyf79a86fc2583be35d35bd7e7cee3899dd8d55b1f1607642353000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.dectrl: increment message IDs for CTRL commands
Implicitly use distinct IDs for CTRL commands. This is a prerequisite
for matching GET_REPLY IDs to GET IDs, to correctly handle CTRL
responses without counting on being lucky.
Rather use 'use_id' as var name instead of overloading the 'id' keyword.
Change-Id: I698faa013eb14f88759685d50d925f5d82d80aa0
2020-12-11 00:19:13 +0100f79a86fc2583be35d35bd7e7cee3899dd8d55b1fctrl: increment message IDs for CTRL commandseditsrc/osmo_gsm_tester/obj/osmo_ctrl.py
- src/osmo_gsm_tester/obj/msc_osmo.pysrc/osmo_gsm_tester/obj/nitb_osmo.pysrc/osmo_gsm_tester/obj/osmo_ctrl.pysrc/osmo_gsm_tester/obj/bsc_osmo.py5b04ef213e8934e4bdf972bd1809ee86742f613d1607643038000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.deOsmoCtrl cleanup: get_var(), set_var(), get_trap()
CTRL interface interaction was mostly inherited from the first legacy
implementation of osmo-gsm-tester, and it was a pain to look at from the
start. Now, while I'm close to the topic, I want this to improve:
Properly match a GET_REPLY/SET_REPLY to a sent GET/SET by the message
ID.
Completely drop the do_get() and do_set(), which were not useful for
correct handling of the CTRL request and response messaging. The API to
use by callers is set_var(), get_var()/get_int_var() and get_trap().
These call the internal _sendrecv() (or for TRAP only _recv())
functions. Make it so that tese work both on an already connected
OsmoCtrl, as well as one that needs to establish a (short) connection,
so that both are trivially possible:
# one CTRL connection stays open
with OsmoCtrl(...) as ctrl:
ctrl.get_var('var1')
ctrl.get_var('var2')
ctrl.get_var('var3')
and
# get_var() opens a connection, does the GET and closes again
OsmoCtrl(...).get_var('var1')
Do away with doubling the instances OsmoCtrl and e.g. OsmoBscCtrl.
Rather make OsmoBscCtrl a child class of OsmoCtrl, which means that we
no longer have bsc.ctrl().ctrl(), just bsc.ctrl().
Have VERB_* constants instead of dup'd strings.
Apply to / simplify all callers of OsmoCtrl.
Some of these changes are similar to recently added OsmoVty.
Change-Id: Id561e5a55d8057a997a8ec9e7fa6f94840194df1
2020-12-11 00:30:38 +01005b04ef213e8934e4bdf972bd1809ee86742f613dOsmoCtrl cleanup: get_var(), set_var(), get_trap()editsrc/osmo_gsm_tester/obj/bsc_osmo.pyeditsrc/osmo_gsm_tester/obj/osmo_ctrl.pyeditsrc/osmo_gsm_tester/obj/nitb_osmo.pyeditsrc/osmo_gsm_tester/obj/msc_osmo.py
- src/osmo_gsm_tester/testenv.pysrc/osmo_gsm_tester/obj/msc_osmo.pysrc/osmo_gsm_tester/obj/nitb_osmo.pysrc/osmo_gsm_tester/obj/bsc_osmo.py012a17da6a0c0628f890786d1b6c4a5ecb18cccd1607643038000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.dekeep Ctrl connections open for bsc, msc and nitb objects
The pattern to use 'with' to keep a CTRL connection open adds indents to
every test script that wants to avoid multiple reconnections to the
CTRL. Instead, keeping a single open connection that is cleaned up on
{bsc,msc,nitb} object cleanup ensures that a) the program started up
successfully and opened a CTRL port, b) always has a CTRL open without
having to worry about it and c) keeps test scripts less
complex/indented/crufted.
(These are all current users of the OsmoCtrl API.)
Change-Id: I53fedbe569c5ccbc4b1a17dafe1f8d1bb8200b24
2020-12-11 00:30:38 +0100012a17da6a0c0628f890786d1b6c4a5ecb18cccdkeep Ctrl connections open for bsc, msc and nitb objectseditsrc/osmo_gsm_tester/testenv.pyeditsrc/osmo_gsm_tester/obj/nitb_osmo.pyeditsrc/osmo_gsm_tester/obj/msc_osmo.pyeditsrc/osmo_gsm_tester/obj/bsc_osmo.py
- selftest/rate_ctrs_test/rate_ctrs_test.pyselftest/rate_ctrs_test/_prep.pyselftest/rate_ctrs_test/rate_ctrs_test.errsrc/osmo_gsm_tester/obj/osmo_ctrl.pyselftest/rate_ctrs_test/rate_ctrs_test.ok5354058c75200728caf4dcdcb2c87754b103d2ca1607643038000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.deosmo_ctrl.py: add RateCounters
First user will be the upcoming handover_2G/handover.py test in
I0b2671304165a1aaae2b386af46fbd8b098e3bd8.
Change-Id: Id799b3bb81eb9c04d13c26ff611e40363920300e
2020-12-11 00:30:38 +01005354058c75200728caf4dcdcb2c87754b103d2caosmo_ctrl.py: add RateCountersaddselftest/rate_ctrs_test/rate_ctrs_test.erraddselftest/rate_ctrs_test/rate_ctrs_test.pyeditsrc/osmo_gsm_tester/obj/osmo_ctrl.pyaddselftest/rate_ctrs_test/rate_ctrs_test.okaddselftest/rate_ctrs_test/_prep.py
- src/osmo_gsm_tester/testenv.pysysmocom/scenarios/bts1-trx-sysmocell5000.confsysmocom/scenarios/bts1-trx-umtrx.confsysmocom/suites/handover_2G/suite.confsysmocom/scenarios/bts1-trx-lms.confsysmocom/scenarios/bts1-sysmo.confsysmocom/scenarios/bts1-trx-lms-limenet-micro.confsysmocom/scenarios/bts1-trx-b200.confsysmocom/scenarios/bts1-octphy.confsysmocom/scenarios/bts1-oc2g.confsysmocom/scenarios/bts1-nanobts.confsysmocom/handover-suites.confsysmocom/suites/handover_2G/handover.pyde6743de9a72a0798896d09f50572b9a9fdc20d21607643677000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.deadd handover_2G suite, with handover.py test
Via VTY, handover two lchans of a voice call from bts0 to bts1 and back.
New scenarios/bts1-* allow selecting various types for bts1,
complementing the already existing files for selecting bts0.
Change-Id: I0b2671304165a1aaae2b386af46fbd8b098e3bd8
2020-12-11 00:41:17 +0100de6743de9a72a0798896d09f50572b9a9fdc20d2add handover_2G suite, with handover.py testaddsysmocom/scenarios/bts1-nanobts.confaddsysmocom/handover-suites.confaddsysmocom/suites/handover_2G/handover.pyaddsysmocom/scenarios/bts1-trx-sysmocell5000.confaddsysmocom/scenarios/bts1-oc2g.confaddsysmocom/scenarios/bts1-trx-umtrx.confaddsysmocom/scenarios/bts1-octphy.confaddsysmocom/scenarios/bts1-trx-lms-limenet-micro.confeditsrc/osmo_gsm_tester/testenv.pyaddsysmocom/scenarios/bts1-trx-lms.confaddsysmocom/suites/handover_2G/suite.confaddsysmocom/scenarios/bts1-sysmo.confaddsysmocom/scenarios/bts1-trx-b200.conf
- sysmocom/default-suites.conf7187510defa64c18a9ae8604abf51cfcd7e27d4b1607643677000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.derun handover_2G in default-suites.conf
Change-Id: Ic6bb013cc2c395211eeb86fe7a3d3f42671793c7
2020-12-11 00:41:17 +01007187510defa64c18a9ae8604abf51cfcd7e27d4brun handover_2G in default-suites.confeditsysmocom/default-suites.conf
- src/osmo_gsm_tester/core/process.pyfb8c02fbd5419f37b5261f3166d8b3b2970e599f1607643677000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.deprocess output: do not leak ANSI colors past logged stdout/stderr
In jenkins, I still saw incidents of the entire log becoming colored
after a colored stderr snippet was printed to the log. Make absolutely
sure that no unterminated ANSI coloring is leaked.
Change-Id: Ib9ac1eea4a12d6d43ac8614491f016bbe9ca17b1
2020-12-11 00:41:17 +0100fb8c02fbd5419f37b5261f3166d8b3b2970e599fprocess output: do not leak ANSI colors past logged stdout/stderreditsrc/osmo_gsm_tester/core/process.py
- src/osmo-gsm-tester.py1e01a68846abd272118a0c539439c3fb4ae39a3d1607643677000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.deadd option osmo-gsm-tester.py --suites-file my-suites-listing.conf
For example, run with '-S handover-suites.conf' to just do the handover
tests.
Change-Id: If896ac84d02a275deda2f20a93c29312df128ebb
2020-12-11 00:41:17 +01001e01a68846abd272118a0c539439c3fb4ae39a3dadd option osmo-gsm-tester.py --suites-file my-suites-listing.confeditsrc/osmo-gsm-tester.py
- src/osmo_gsm_tester/obj/osmo_ctrl.pyf80f7cc5c46bddf63c0f41042f28e7f62aec45af1607643677000https://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrneels@hofmeyr.deOsmoCtrl: use one global common counter for CTRL IDs
It is easier to traverse debugging logs if the CTRL request and response
IDs are globally unique across all programs and tests. Before this, we
were using 0 almost everywhere.
(This is not strictly needed for correctness, since each CTRL client has
its own request ID scope; just we open fairly many separate CTRL clients
all the time in our tests.)
Change-Id: I44c51f4fb5beb6cedf98ea0d6684a24c6aa418c7
2020-12-11 00:41:17 +0100f80f7cc5c46bddf63c0f41042f28e7f62aec45afOsmoCtrl: use one global common counter for CTRL IDseditsrc/osmo_gsm_tester/obj/osmo_ctrl.py
- sysmocom/resources.conf.prod7ecfaa6a0f970ff22520feeda97ca5920e7a06141607689708000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@espeweb.netsysmocom resources.conf.prod: Update modem paths + add new modems after HW upgrade
Change-Id: I346a5bb38270a32695ec73994179bd75d873b67a
2020-12-11 13:28:28 +01007ecfaa6a0f970ff22520feeda97ca5920e7a0614sysmocom resources.conf.prod: Update modem paths + add new modems after HW upgradeeditsysmocom/resources.conf.prod
- src/osmo_gsm_tester/core/resource.py2c92c2e9be4ad301b03649071aa6f7b4bc057bbe1608216699000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@espeweb.netresource: Fix next_zmq_port_range using bvci file name
Change-Id: I293b7de1066ea69ccb0e495a69602ed56810018d
2020-12-17 15:51:39 +01002c92c2e9be4ad301b03649071aa6f7b4bc057bberesource: Fix next_zmq_port_range using bvci file nameeditsrc/osmo_gsm_tester/core/resource.py
- sysmocom/resources.conf.virtual929a4f963c2c7927b72bd41eb737cc92c53547de1608571532000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@espeweb.netsysmocom/resources.conf.virtual: remove no longer existing arfcn resources
ARFCN are not resources anymore since a recent commit.
Fixes: ecce402f43b708bf178d603e2bd8587e72fdb3b1
Change-Id: Icc0971b285e8db085670808b7d7bb98c38db2753
2020-12-21 18:25:32 +0100929a4f963c2c7927b72bd41eb737cc92c53547desysmocom/resources.conf.virtual: remove no longer existing arfcn resourceseditsysmocom/resources.conf.virtual
- sysmocom/suites/netreg_mass/suite.confsysmocom/suites/nitb_netreg_mass/register_default_mass.pysysmocom/suites/netreg_mass/register_default_mass.pysysmocom/suites/nitb_netreg_mass/suite.confd95d494fcc1979299c19cd337fdfb21ae77739e61608571963000https://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrolpespin@espeweb.netsysmocom: Port nitb_netreg_mass suite to osmo split network
Change-Id: I221df84d76f73e15eed98036b31adc8089c8dc99
2020-12-21 18:32:43 +0100d95d494fcc1979299c19cd337fdfb21ae77739e6sysmocom: Port nitb_netreg_mass suite to osmo split networkaddsysmocom/suites/netreg_mass/suite.confaddsysmocom/suites/netreg_mass/register_default_mass.pydeletesysmocom/suites/nitb_netreg_mass/suite.confdeletesysmocom/suites/nitb_netreg_mass/register_default_mass.py
- contrib/jenkins-build-srslte.sh4cd6f14be2908230ad52d138d8a9697103c47eca1610033425000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comjenkins-build-srslte.sh: allow custom binaries
this allows to specify the environmental var
wanted_binaries_bin that will be included in the
trial package. if the variable isn't set, all three
main srsLTE binaries are included
Change-Id: I63f5799328435ce32b5bfd6dae6fd0b37e1e5397
2021-01-07 16:30:25 +01004cd6f14be2908230ad52d138d8a9697103c47ecajenkins-build-srslte.sh: allow custom binarieseditcontrib/jenkins-build-srslte.sh
- src/osmo_gsm_tester/templates/srsenb_drb.conf.tmpla7725fcedf5f22895897e08e7a9d62bedbb7fff41610033425000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comsrsenb_drb.conf.tmpl: add QCI1 DRB config
use default QCI1 config for real-time voice traffic
Change-Id: I43f408b1a3c172a5eb8327f03df49801e063e5cd
2021-01-07 16:30:25 +0100a7725fcedf5f22895897e08e7a9d62bedbb7fff4srsenb_drb.conf.tmpl: add QCI1 DRB configeditsrc/osmo_gsm_tester/templates/srsenb_drb.conf.tmpl
- src/osmo_gsm_tester/obj/enb.pybfd3fe659e4e8bac99e7530e71126ca5be57d1211610033425000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comenb: include name label and run_addr in enb remote path
this allows to quickly identify the enb host in the logs
Change-Id: I9c979de852a23041e43692e97ebcbfb389b52fdb
2021-01-07 16:30:25 +0100bfd3fe659e4e8bac99e7530e71126ca5be57d121enb: include name label and run_addr in enb remote patheditsrc/osmo_gsm_tester/obj/enb.py
- src/osmo_gsm_tester/templates/srsue.conf.tmpl507c60ca0c2b3a6be9c506e22de5670db9f009fa1610033425000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comsrsue.conf.tmpl: reorder conditions for setting RRC release
the order of checks needs to go from high to low, i.e. the higher
release feature (e.g. qam256) needs to be checked and set first.
in theory it should also be possible to have a CA-capable UE
that does not support QAM256, but for srsUE we announce both anyway.
Change-Id: I2fa49f0cb5d80db412a811ceeb380359c8ad67a7
2021-01-07 16:30:25 +0100507c60ca0c2b3a6be9c506e22de5670db9f009fasrsue.conf.tmpl: reorder conditions for setting RRC releaseeditsrc/osmo_gsm_tester/templates/srsue.conf.tmpl
- sysmocom/scenarios/mod-enb-cells-intraenb-intrafreq-ho.confeee4f5f715199cae9ba2def407aed4ba7177d6fc1610033425000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comintraenb-intrafreq-ho.conf: add eNB to cell config
make sure to have the right eNB that matches the
cells neighbor ECIDs, otherwise the eNB may trigger
a S1 HO if the eNB ID is set elsewhere
Change-Id: Id494ac1984846e78a6456bb6a17e72d63c9dacf5
2021-01-07 16:30:25 +0100eee4f5f715199cae9ba2def407aed4ba7177d6fcintraenb-intrafreq-ho.conf: add eNB to cell configeditsysmocom/scenarios/mod-enb-cells-intraenb-intrafreq-ho.conf
- src/osmo_gsm_tester/templates/srsue.conf.tmpl1d1c0bfed93811280da2fae90e9c078a682d70421610033425000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comsrsue.conf.tmpl: disable TTI stats for ZMQ
since ZMQ runs are not using wall clock anyway, measuring
TTI execution isn't useful, disable it therefore to avoid
misleading warnings.
Change-Id: I5c2cb0abcfce0ee67806f6611356f4d5d180541d
2021-01-07 16:30:25 +01001d1c0bfed93811280da2fae90e9c078a682d7042srsue.conf.tmpl: disable TTI stats for ZMQeditsrc/osmo_gsm_tester/templates/srsue.conf.tmpl
- src/osmo_gsm_tester/obj/enb_srs.pyb7ce9499b61e6d8b4556e70aefb768a95ec1ad2e1610048627000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comenb_srs: only use QAM64 tables if both UE and eNB are configured for QAM64
this was causing failed tests because to achieve QAM64 rates both
eNB and UE need to support it and have it activated.
Change-Id: I599df92d69eeb56a5d44327de08f004222cff073
2021-01-07 20:43:47 +0100b7ce9499b61e6d8b4556e70aefb768a95ec1ad2eenb_srs: only use QAM64 tables if both UE and eNB are configured for QAM64editsrc/osmo_gsm_tester/obj/enb_srs.py
- src/osmo_gsm_tester/obj/enb_srs.py2df63d0f2fb2065633c4d7e1038a61803989d6ed1610048627000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comenb_srs: adopt throughput thresholds for QAM256
it turned out that we have to reduce the MCS when using QAM256,
especially for 6 PRB as subframe 0 and 5 contains PBCH and PSS
signals, so the available REs are reduced.
The eNB scheduler now has this limitation in mind and lowers the MCS.
Change-Id: I0e38fe28002fd68c768cc8dcffcf74f4f190df02
2021-01-07 20:43:47 +01002df63d0f2fb2065633c4d7e1038a61803989d6edenb_srs: adopt throughput thresholds for QAM256editsrc/osmo_gsm_tester/obj/enb_srs.py
- src/osmo_gsm_tester/templates/srsepc.conf.tmpl9c7fd618d226dc532b9408c329cfc2380de4850a1610048627000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comsrsepc.conf.tmpl: increase default value of T3413 (paging timer)
we've seen that the default value of 2s might be a bit tight.
the value is network dependent so no real default value exists.
however, 6s seems to be a good compromise.
Change-Id: Icc75ee048c2cc605ab26c4c87a039519998f7e57
2021-01-07 20:43:47 +01009c7fd618d226dc532b9408c329cfc2380de4850asrsepc.conf.tmpl: increase default value of T3413 (paging timer)editsrc/osmo_gsm_tester/templates/srsepc.conf.tmpl
- src/osmo_gsm_tester/templates/srsenb.conf.tmpl4cb9ab56715ac69c659eccada59bf9c6356416e11610048628000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comsrsenb.conf.tmpl: set nof_of_prach_threds to 0 for ZMQ
this executed the PRACH search in the main thread so
PHY workers and PRACH processing don't diverge in loaded
scenarios
Change-Id: I97eddb5f9ca682251ded1f73093c2d0a49462bd6
2021-01-07 20:43:48 +01004cb9ab56715ac69c659eccada59bf9c6356416e1srsenb.conf.tmpl: set nof_of_prach_threds to 0 for ZMQeditsrc/osmo_gsm_tester/templates/srsenb.conf.tmpl
- utils/bin/osmo-gsm-tester_androidue_conn_chk.shsrc/osmo_gsm_tester/obj/android_host.pysrc/osmo_gsm_tester/obj/run_node.pysysmocom/scenarios/ms-label.confsrc/osmo_gsm_tester/core/schema.pyutils/bin/osmo-gsm-tester_androidue_diag_parser.shsrc/osmo_gsm_tester/obj/ms.pysrc/osmo_gsm_tester/obj/ms_android.pysrc/osmo_gsm_tester/obj/android_apn.pysrc/osmo_gsm_tester/obj/qc_diag.pysrc/osmo_gsm_tester/obj/android_bitrate_monitor.pysrc/osmo_gsm_tester/obj/iperf3.pysrc/osmo_gsm_tester/core/process.pya8263f40e9c3baf4a6ba34b213ff2fe87c0993fd1610563556000https://jenkins.osmocom.org/jenkins/user/nils.fuerstenils.fuerstenils.fuerste@rub.deIntroduce Android UEs as new modems
To expand the test capacities we would like to introduce
Android UEs as new modems. Currently the following tests
are supported:
- Ping
- iPerf3 DL/UL
- RRC Mobile MT Ping
In the following is a small description.
Prerequisites:
- Android UE
- Rooted (Ping, iPerf, RRC Idle MT Ping)
- Qualcomm baseband with working diag_mdlog (RRC Idle MT Ping)
- iPerf3
- Dropbear
- OGT Slave Unit
- Android SDK Platform-Tools
(https://developer.android.com/studio/releases/platform-tools#downloads)
- Pycrate (https://github.com/P1sec/pycrate)
- SCAT
clone https://github.com/bedrankara/scat/ & install dependencies
checkout branch ogt
symlink scat (ln -s ~/scat/scat.py /usr/local/bin/scat)
Infrastructure explaination:
The Android UEs are connected to the OGT Units via USB. We
activate tethering and set up a SSH server (with Dropbear).
We chose tethering over WiFi to have a more stable route
for the ssh connection. We forward incoming connections to
the OGT unit hosting the Android UE(s) on specific ports
to the UEs via iptables. This enables OGT to issue commands
directly to the UEs. In case of local execution we use ADB
to issue commands to the AndroidUE. The set up was tested
with 5 Android UEs connected in parallel but it should be
scalable to the number of available IPs in the respective
subnet. Furthermore, we need to cross compile Dropbear
and iPerf3 to use them on the UEs. These tools have to be
added to the $PATH variable of the UEs.
Examplary set up:
In this example we have two separate OGT units (master
and slave) and two Android UEs that are connected to the
slave unit. An illustration may be found here: https://ibb.co/6BXSP2C
On UE 1:
ip address add 192.168.42.130/24 dev rndis0
ip route add 192.168.42.0/24 dev rndis0 table local_network
dropbearmulti dropbear -F -E -p 130 -R -T /data/local/tmp/authorized_keys -U 0 -G 0 -N root -A
On UE 2:
ip address add 192.168.42.131/24 dev rndis0
ip route add 192.168.42.0/24 dev rndis0 table local_network
dropbearmulti dropbear -F -E -p 131 -R -T /data/local/tmp/authorized_keys -U 0 -G 0 -N root -A
On OGT slave unit:
sudo ip link add name ogt type bridge
sudo ip l set eth0 master ogt
sudo ip l set enp0s20f0u1 master ogt
sudo ip l set enp0s20f0u2 master ogt
sudo ip a a 192.168.42.1/24 dev ogt
sudo ip link set ogt up
Now we have to manually connect to every UE from OGT Master
to set up SSH keys and verify that the setup works.
Therefore, use:
ssh -p [UE-PORT] root@[OGT SLAVE UNIT's IP]
Finally, to finish the setup procedure create the
remote_run_dir for Android UEs on the slave unit like
following:
mkdir /osmo-gsm-tester-androidue
chown jenkins /osmo-gsm-tester-androidue
Example for modem in resource.conf:
- label: mi5g
type: androidue
imsi: '901700000034757'
ki: '85E9E9A947B9ACBB966ED7113C7E1B8A'
opc: '3E1C73A29B9C293DC5A763E42C061F15'
apn:
apn: 'srsapn'
mcc: '901'
mnc: '70'
select: 'True'
auth_algo: 'milenage'
features: ['4g', 'dl_qam256', 'qc_diag']
run_node:
run_type: ssh
run_addr: 100.113.1.170
ssh_user: jenkins
ssh_addr: 100.113.1.170
ue_ssh_port: 130
adb_serial_id: '8d3c79a7'
scat_parser:
run_type: local
run_addr: 127.0.0.1
adb_serial_id: '8d3c79a7'
Example for default-suites.conf:
- 4g:ms-label@mi5g+srsenb-rftype@uhd+mod-enb-nprb@25+mod-enb-txmode@1
Change-Id: I79a5d803e869a868d4dac5e0d4c2feb38038dc5c
2021-01-13 19:45:56 +0100a8263f40e9c3baf4a6ba34b213ff2fe87c0993fdIntroduce Android UEs as new modemseditsrc/osmo_gsm_tester/obj/ms.pyeditsrc/osmo_gsm_tester/obj/iperf3.pyaddutils/bin/osmo-gsm-tester_androidue_diag_parser.shaddsrc/osmo_gsm_tester/obj/android_host.pyaddsrc/osmo_gsm_tester/obj/ms_android.pyaddsysmocom/scenarios/ms-label.confeditsrc/osmo_gsm_tester/core/schema.pyaddsrc/osmo_gsm_tester/obj/android_bitrate_monitor.pyeditsrc/osmo_gsm_tester/core/process.pyaddsrc/osmo_gsm_tester/obj/qc_diag.pyeditsrc/osmo_gsm_tester/obj/run_node.pyaddutils/bin/osmo-gsm-tester_androidue_conn_chk.shaddsrc/osmo_gsm_tester/obj/android_apn.py
- src/osmo_gsm_tester/obj/enb_srs.pysrc/osmo_gsm_tester/obj/enb.pysrc/osmo_gsm_tester/obj/srslte_common.pysrc/osmo_gsm_tester/obj/enb_amarisoft.pysrc/osmo_gsm_tester/obj/ms_srs.pysrc/osmo_gsm_tester/core/process.pyf249a026a06812c667e037eb1b609d48922e13d71612802889000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comenb,ue,process: move stdout counter helper to process objects
this patch adds the stdout counter to count events happening
on the stdout (known from the UE already) to the common
process class so they can also be used from the eNB (and other objects)
In addition, we add a PRACH counter to be used for tests.
Change-Id: I434f072b8aa6f4dce9f90889c6b40832f6798ff8
2021-02-08 17:48:09 +0100f249a026a06812c667e037eb1b609d48922e13d7enb,ue,process: move stdout counter helper to process objectseditsrc/osmo_gsm_tester/obj/ms_srs.pyeditsrc/osmo_gsm_tester/obj/srslte_common.pyeditsrc/osmo_gsm_tester/core/process.pyeditsrc/osmo_gsm_tester/obj/enb_amarisoft.pyeditsrc/osmo_gsm_tester/obj/enb_srs.pyeditsrc/osmo_gsm_tester/obj/enb.py
- sysmocom/suites/4g/rrc_idle_mo_ping.pysysmocom/suites/4g/rrc_idle_mt_ping.py29263b7389520ec2269d6852a09f96ef8da795731612802889000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.com4g: add checks for received PRACHs for ping tests
the tests already check for sent PRACHs, this will
also check for received PRACHs on the eNB to make
sure we don't detect any fake PRACHs during the tests.
Change-Id: Ib23056b1ad4b18a7dde6cd0c997f5114ac2acb61
2021-02-08 17:48:09 +010029263b7389520ec2269d6852a09f96ef8da795734g: add checks for received PRACHs for ping testseditsysmocom/suites/4g/rrc_idle_mo_ping.pyeditsysmocom/suites/4g/rrc_idle_mt_ping.py
- src/osmo_gsm_tester/obj/enb.pysrc/osmo_gsm_tester/obj/enb_srs.pysrc/osmo_gsm_tester/obj/srslte_common.pysrc/osmo_gsm_tester/obj/enb_amarisoft.py215bec2f3caca938e510f5d77e5b74dee343fbc21612802889000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comenb: add abstract method stop()
implement as noop for Amarisoft eNB, srsENB will send q+Enter to stdin,
which is implemented in class srslte_common()
Change-Id: Ide606e1a6b523997215aa2fa39d4d56ae1f49181
2021-02-08 17:48:09 +0100215bec2f3caca938e510f5d77e5b74dee343fbc2enb: add abstract method stop()editsrc/osmo_gsm_tester/obj/enb_amarisoft.pyeditsrc/osmo_gsm_tester/obj/enb.pyeditsrc/osmo_gsm_tester/obj/enb_srs.pyeditsrc/osmo_gsm_tester/obj/srslte_common.py
- sysmocom/scenarios/mod-enb-integrity@.confsrc/osmo_gsm_tester/obj/bts.pysrc/osmo_gsm_tester/obj/enb_amarisoft.pysysmocom/defaults.confsrc/osmo_gsm_tester/obj/enb.pysrc/osmo_gsm_tester/templates/srsenb.conf.tmplsrc/osmo_gsm_tester/templates/amarisoft_enb.cfg.tmplsrc/osmo_gsm_tester/core/schema.pysysmocom/scenarios/mod-enb-cipher@.confsrc/osmo_gsm_tester/obj/ms.pya81801558e7bb6ef0f0a32ab078d302c91e940a81612802889000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comenb: Set cipher and integrity via scenario file
This patch enables setting cipher and integrity algorithms
in Amarisoft eNB and srsENB via scenario files. If no
settings are defined following defaults are applied:
- Cipher algorithm: EEA0, EEA2, EEA1
- Integrity algorithm: EIA2, EIA1, EIA0
Example of setting cipher algorithms:
- 4g:srsue-rftype@uhd+srsenb-rftype@uhd+mod-enb-cipher@eea1+mod-enb-cipher@eea0+mod-enb-nprb@6
Change-Id: I595206b7d49016fb6d0aec175c828d9537c53886
2021-02-08 17:48:09 +0100a81801558e7bb6ef0f0a32ab078d302c91e940a8enb: Set cipher and integrity via scenario fileeditsrc/osmo_gsm_tester/obj/ms.pyeditsrc/osmo_gsm_tester/templates/srsenb.conf.tmpleditsrc/osmo_gsm_tester/obj/bts.pyeditsrc/osmo_gsm_tester/obj/enb_amarisoft.pyeditsrc/osmo_gsm_tester/obj/enb.pyaddsysmocom/scenarios/mod-enb-integrity@.confeditsysmocom/defaults.confeditsrc/osmo_gsm_tester/templates/amarisoft_enb.cfg.tmpleditsrc/osmo_gsm_tester/core/schema.pyaddsysmocom/scenarios/mod-enb-cipher@.conf
- sysmocom/scenarios/mod-enb-cells-2ca.confsysmocom/scenarios/mod-enb-ncells@.confsysmocom/scenarios/mod-enb-cells-intra-freq-ho-sameport.confsysmocom/scenarios/mod-enb-cells-intraenb-intrafreq-ho.confb79a0c5e75dda5c08f8fa5dd9bcd6a8bcea106c71612802889000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comscenarios: remove ncells@ scenario and define number of cells explicitly
the specific cell scenarios files already contain cell-related
information so having a extra ncells scenario seems too much overhead.
furthermore, in more complex tests its helps to reduce the filename/path
lenght to avoid hitting the 255 character limit
Change-Id: If022d9e8d239805ee1280fb52660e68dda7484a0
2021-02-08 17:48:09 +0100b79a0c5e75dda5c08f8fa5dd9bcd6a8bcea106c7scenarios: remove ncells@ scenario and define number of cells explicitlyeditsysmocom/scenarios/mod-enb-cells-intra-freq-ho-sameport.confeditsysmocom/scenarios/mod-enb-cells-intraenb-intrafreq-ho.confeditsysmocom/scenarios/mod-enb-cells-2ca.confdeletesysmocom/scenarios/mod-enb-ncells@.conf
- src/osmo_gsm_tester/templates/srsepc.conf.tmplsysmocom/suites/4g/rrc_idle_mt_ping.pyd1732d78205c164e0ed9f2db8b3510537879796d1612802889000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comsrsepc.conf.tmpl: double value of T3413 (paging timer)
we've already incrased the t3413 value in 9c7fd618d226dc532b9408c329cfc2380de4850a
but realized it may still be too low in some cases.
we set it to 12s now.
Change-Id: I9c3c59c0ff8f539a44b420f8ba31eea016c211ce
2021-02-08 17:48:09 +0100d1732d78205c164e0ed9f2db8b3510537879796dsrsepc.conf.tmpl: double value of T3413 (paging timer)editsrc/osmo_gsm_tester/templates/srsepc.conf.tmpleditsysmocom/suites/4g/rrc_idle_mt_ping.py
- src/osmo_gsm_tester/templates/srsue.conf.tmpl7aa14e45f455f87c1dfe9966d759093af9f6d6fc1612802889000https://jenkins.osmocom.org/jenkins/user/andreandreandre@softwareradiosystems.comsrsue.conf.tmpl: reduce nof PHY threads to 2 for ZMQ
we've detected a possible race condition during the Msg3
transmission that caused the thread that sets the Msg3 grant
to be delayed. The PHY worker that executed TTI+2 finished
by that time already and didn't even see the pending UL grant.
This is issue is more likely to happen on loaded system,
for example when running parallel ZMQ jobs. We therefore decided
to reduce the number of parallel PHY workers to 2 so the issue
is circumvented.
Change-Id: Ibdb42a1705d87b6d343201458c8fe397398802bc
2021-02-08 17:48:09 +01007aa14e45f455f87c1dfe9966d759093af9f6d6fcsrsue.conf.tmpl: reduce nof PHY threads to 2 for ZMQeditsrc/osmo_gsm_tester/templates/srsue.conf.tmpl
githttps://jenkins.osmocom.org/jenkins/user/andreandrehttps://jenkins.osmocom.org/jenkins/user/fixeriaVadim Yanitskiyhttps://jenkins.osmocom.org/jenkins/user/nils.fuerstenils.fuerstehttps://jenkins.osmocom.org/jenkins/user/osmithOliver Smithhttps://jenkins.osmocom.org/jenkins/user/neelsNeels Hofmeyrhttps://jenkins.osmocom.org/jenkins/user/pmaierpmaier@sysmocom.dehttps://jenkins.osmocom.org/jenkins/user/zeckeHolger Freytherhttps://jenkins.osmocom.org/jenkins/user/holgerholgerhttps://jenkins.osmocom.org/jenkins/user/laforgelaforgehttps://jenkins.osmocom.org/jenkins/user/pespinPau Espin Pedrol