diff options
| author | Neels Hofmeyr <neels@hofmeyr.de> | 2020-11-25 22:56:13 +0000 |
|---|---|---|
| committer | Neels Hofmeyr <neels@hofmeyr.de> | 2020-11-26 01:04:57 +0000 |
| commit | 9ebabc8b0e32dee5e25dbb52b4756e0881a5e4bf (patch) | |
| tree | 5a793a72fa73cf072f53570a0368e2a438775ae1 /gbproxy | |
| parent | c897cfb6e60f1ded3a0c5c4009cf329760a8666c (diff) | |
vty: log failed vty command
Add a log label argument to f_vty_wait_for_prompt(), and feed the sent
command from f_vty_transceive*(), so that the failure verdict already
lists the vty command that caused the failure.
A common error is to issue insufficient 'exit' commands, so that I often
think the newly added VTY command failed, even though it is a subsequent
command causing the failure. I want to shorten the "time-to-aha" there.
Change-Id: Icfd739db150d86e9256a224f12dc979dcd77879f
Diffstat (limited to 'gbproxy')
0 files changed, 0 insertions, 0 deletions