Skip to content
Sign in
Unstable

Changes

Summary

  1. s1gw: add MME pool related REST definitions (details)
  2. bts: testenv: check ulimit -r in prepare= (details)
  3. testenv: less cluttered output for failed cmds (details)
Commit 26153b11a07cba86bfd5865ac7d75c4f006b6c16 by Vadim Yanitskiy
s1gw: add MME pool related REST definitions

Change-Id: I76f1a5cf41331d021c08fbefdf78e34da4ac2121
Related: osmo-s1gw.git Iad249aed99face9e35fd19e0596cf2364ade4c77
Related: SYS#7052, SYS#7066
The file was modifieds1gw/S1GW_REST_Types.ttcn
The file was modifieds1gw/S1GW_REST_Functions.ttcn
Commit 62483ef084d8176c64f69eadd1014a3742f90f70 by Oliver Smith
bts: testenv: check ulimit -r in prepare=

Don't respawning over and over again if osmo-bts-trx fails to start up
because the user isn't allowed to set the rtpriority. Show instructions
for fixing it instead.

Change-Id: I7bc1414f95e4a54a40eb7c6f7b3d6c83ce3500c6
The file was modifiedbts/testenv_hopping.cfg
The file was modified_testenv/README.md
The file was modified_testenv/testenv/podman.py
The file was modifiedbts/testenv_oml.cfg
The file was modifiedbts/testenv_generic.cfg
The file was added_testenv/data/scripts/require_ulimit_r.sh
Commit 648954ff1ab94620833b484d8131d001c61faa78 by Oliver Smith
testenv: less cluttered output for failed cmds

The testenv.cmd.run() already prints the command to run at the start,
prints the command output and blocks until the command is done.

If the command fails, do not print the command again, and do not print a
python stack trace. The reason for the failure is most likely in the
output shown by the program itself (e.g. a prepare= script that failed).
Make it easier for the user to spot this error by uncluttering the
output.

Change-Id: I508322b017e5ed9c21396384ef759a4c49c8d3da
The file was modified_testenv/testenv/cmd.py