FYI. I don't see any commit until the last one from Pau on August 13. It could of course also be a change in libosmocore?
Hi,
it seems related to libosmocore d0b3b9edac978c91bf84aa2537aa24426685b1fb, where logp VTY command is added
Mismatch: Expect: ' show talloc-context (application|all) (full|brief|DEPTH)' Got: ' logp (main|db|auc|ss|lglobal|llapd|linp|lmux|lmi|lmib|lsms|lctrl|lgtp|lstats|lgsup|loap|lss7|lsccp|lsua|lm3ua|lmgcp|ljibuf|lrspro) (debug|info|notice|error|fatal) .LOGMESSAGE'
The problem is osmo-hlr test_node.vty doesn't skip library-related commands, so updating the lib can trigger this kind of issues.
Quick fix is in libosmocore. Move the new command upwards:
Expected: [ OsmoHLR> list show version show online-help list exit help enable terminal length <0-512> terminal no length who show history logging enable ... show logging vty show alarms <------ logp appears here after "show alarms" nowadays. show talloc-context (application|all) (full|brief|DEPTH) show talloc-context (application|all) (full|brief|DEPTH) tree ADDRESS show talloc-context (application|all) (full|brief|DEPTH) filter REGEXP show stats show stats level (global|peer|subscriber) show asciidoc counters show rate-counters show gsup-connections subscriber (imsi|msisdn|id|imei) IDENT show show subscriber (imsi|msisdn|id|imei) IDENT ]
I submitted a patch to fix the issue: https://gerrit.osmocom.org/c/libosmocore/+/15244 vty: Register logp cmd next to logging commands