diff options
author | Neels Hofmeyr <neels@hofmeyr.de> | 2019-07-29 19:28:08 +0200 |
---|---|---|
committer | Neels Hofmeyr <neels@hofmeyr.de> | 2019-08-13 15:35:02 +0200 |
commit | d0b3b9edac978c91bf84aa2537aa24426685b1fb (patch) | |
tree | 8c2d63078f1d16411567948d10951a2158873854 /libosmocoding.pc.in | |
parent | c144f3a781d77e241a9bf188ad54890f0a3c6fdf (diff) |
add vty logp command to echo on all log targets
When reading SUT logs resulting from TTCN3 runs, it can be hard to figure out
which log section corresponds to which test code. Add a 'logp' command on VIEW
and ENABLE nodes that simply echos an arbitrary message on log output, useful
to set markers / explanations from the TTCN3 code, which then appear in all log
outputs and can make it trivial to figure out which log section is interesting.
logging_vty_test# logp lglobal notice This is the log message
DLGLOBAL NOTICE This is the log message
From TTCN3, could be used like this, e.g. in BSC_Tests.ttcn:
private function f_logp(charstring log_msg) runs on MSC_ConnHdlr
{
// log on TTCN3 log output
log(log_msg);
// log in stderr log
f_vty_transceive(BSCVTY, "logp lglobal notice " & log_msg);
}
...
f_logp("f_probe_for_handover(" & log_label & "): Ending the test: Handover Failure stops the procedure.");
Change-Id: Ife5dc8999174c74e0d133729284fe526d6eaf8d9
Diffstat (limited to 'libosmocoding.pc.in')
0 files changed, 0 insertions, 0 deletions