Some Amarisoft bundles may come without lteue in it. Allow the script to
run if that's the case by setting an envvar.
Change-Id: I363b44cd8aa48f80d24219b6bf5b3ebde580e3c3
srsEPC expect zero-padding MNC/MCC in config file. However,
001 and mcc will end up as 1 in the rendered template.
Therefore, they need to be formatted correctly.
Change-Id: Ie63cd1b15b961e493a6dcbd7e5a4fbabe0bb6f33
when phy.signal=1 is set in the log_options, the eNB will dump
a binary file that needs to be copied back as well
Change-Id: I63d13cb74572ac065d5a3fcfb1632552d0a6dbc6
this avoids issues when the channel emulation stops in the middle
of a high attenuation values and the device is left in this state.
Change-Id: I9aeafc68bf81b8932aac4cb28040b9aea6bfcbdb
This object allows to run the "stress" cmdline program in the background
on the specifies run_node, to simulate system load.
To run stress, a test can simply do:
stress = tenv.stress(epc.run_node())
stress.start(cpu_workers=2, mem_workers=1, io_workers=1)
And the test environment will remember to stop it when the test finishes.
Change-Id: I21023e6c64c48109f294291bfe3d8d8f4e1de038
this method uses the kpi_analyzer module for analyzing
stdout, CSV metrics and the logfile (if present).
if the module can't be loaded, no KPI will be added.
Change-Id: I28226a375f9ac4e08424c488062ae6a74a19af92
New patchelf 0.11 release is out and it has fixes hitting us in both 0.9
and 0.10 on different binaries. So let's simply requiring having
patchelf 0.11 in all cases and be done with it (actually, if not running
4G binaries, using 0.9 is enough).
Related: OS#4389
Change-Id: I2701e46e7710db4c923a68e6b3a2f3c7b126f356
every call to verify_metrics would copy back metrics again. see log here:
23:29:22.149299 run srsue(pid=31521): Terminating (SIGINT)
23:29:22.368263 run srsue(pid=31521): Terminated: ok {rc=0}
23:29:28.401035 run scp-back-metrics(pid=32265): Launched
23:29:29.423083 run scp-back-metrics(pid=32265): Terminated: ok {rc=0}
23:29:29.490275 run scp-back-metrics(pid=32271): Launched
23:29:30.513852 run scp-back-metrics(pid=32271): Terminated: ok {rc=0}
23:29:30.550862 run scp-back-metrics(pid=32277): Launched
23:29:31.573962 run scp-back-metrics(pid=32277): Terminated: ok {rc=0}
this patch only copies back metrics only once. also make sure that, similar
to logs, metrics are always copied back at the end of the run even if they
are not used for metrics checking. this is needed to run the plotting
script.
Change-Id: Ie7c156a5b2c8768bf90ff8e86515976e0d454c25
In order to set up the channel emulator we need to calculate the total
number of RF channels that a eNB has from within a test.
Change-Id: If641993033eb5dcdc6e2d6afdc8426ed322241ca
this is helpful to run some action for the exact run time of an iperf3
session. note that if no time spec is given when calling
"prepare_test_proc()", a modifier could set the runtime of an DL experiment
to an arbitrary value so we need to have a mechanism to read
the actual time from within a test
Change-Id: I484a0add322ffd269a1e9df72a00cf348950b268
Currently osmo-gsm-tester master jenkins build fails while building
manual due to errors like:
"asciidoc: WARNING: test_api.adoc: line 42: no callouts refer to list
item 1"
According to asciidoc documentation in [1], code examples can be
annotated with callouts, but callouts need to be put inside source code
comments.
[1] http://www.methods.co.nz/asciidoc/chunked/ch20.html
Change-Id: I2213874592342b12adf7440b25edc706abfc78ba
tests can now use 'tenv.test().set_kpis(some_dict)' to set any kind of
data as KPIs, which will be presented in the junit report.
The representation of KPIs in the xml file doesn't follow the junit
format, mainly because it has no support for per-test properties.
Change-Id: I00e976f65a202e82d440bf33708f06c8ce2643e2
10s was too short and has still caused tests to fail because they were
stopped just before the iperf finished.
30s seems to be enought and has passed multiple times so far
Change-Id: I80b732a060356aa98882ff0e8b5debaf623ba0fb
this refactor no longer enforces blocking operation of the process.
Instead it returns the process object to the caller who
can now run either proc.launch() for non-blocking operation
or proc.launch_sync() for blocking mode.
The non-block mode allos doing other stuff in the background,
for example controlling the rfemu while running a ping.
Change-Id: Ia6372e55a8829f722e40db537d9dfd63a94d1be9
Timeout value can be specified by test in suite.conf:
config:
suite:
<suite_name>:
<test_name>:
timeout: 2 # 2 seconds timeout
Change-Id: I522f51f77f8be64ebfdb5d5e07ba92baf82d7706
This feature is not really implemented and maybe never was. In any case,
it makes sense to have that working per-test so we can specify different
values per test in case it's needed.
Change-Id: I3c1b95c10e974da87ec9abd25578d8bcc0bc55a3
process object always used timeout=300 while runnig wth launch_sync().
Let's allow replacing that value beforehand so that iperf3 can
pre-configure the process object and caller doesn't need to care about
calculating expected time.
Change-Id: I7f6c5078f648013515919aa35ebcdb3ef157b5e4
Otherwise processes using the link like "ping" or "iperf3" may fail
because there's still no IP address assigned.
Change-Id: I28137f10a19db01fe90b24830a60342a448d1e92
Pau Espin
Andre Puschmann