From 143b02c573ffafbc04301ee539150ec0c936a3e9 Mon Sep 17 00:00:00 2001 From: Daniel Hahler Date: Sun, 11 Aug 2019 13:18:29 +0200 Subject: vim-patch:8.1.1461: tests do not run or are not reliable on some systems Problem: Tests do not run or are not reliable on some systems. Solution: Use "findstr" instead of "grep" on MS-Windows. Clear PROMPT_COMMAND in the terminal test. Delete temp file. Wait for output after executing a debug command. (Yegappan Lakshmanan, closes vim/vim#4479) https://github.com/vim/vim/commit/ddd3308782e931a2c390d692cb23c40d8169bd6f Ignored changes to testdir/test_terminal.vim. --- src/nvim/testdir/test_debugger.vim | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) (limited to 'src/nvim/testdir/test_debugger.vim') diff --git a/src/nvim/testdir/test_debugger.vim b/src/nvim/testdir/test_debugger.vim index c923b22836..bb87ef9c58 100644 --- a/src/nvim/testdir/test_debugger.vim +++ b/src/nvim/testdir/test_debugger.vim @@ -52,16 +52,16 @@ func Test_Debugger() let buf = RunVimInTerminal('-S Xtest.vim', {}) " Start the Vim debugger - call RunDbgCmd(buf, ':debug echo Foo()') + call RunDbgCmd(buf, ':debug echo Foo()', ['cmd: echo Foo()']) " Create a few stack frames by stepping through functions - call RunDbgCmd(buf, 'step') - call RunDbgCmd(buf, 'step') - call RunDbgCmd(buf, 'step') - call RunDbgCmd(buf, 'step') - call RunDbgCmd(buf, 'step') - call RunDbgCmd(buf, 'step') - call RunDbgCmd(buf, 'step') + call RunDbgCmd(buf, 'step', ['line 1: let var1 = 1']) + call RunDbgCmd(buf, 'step', ['line 2: let var2 = Bar(var1) + 9']) + call RunDbgCmd(buf, 'step', ['line 1: let var1 = 2 + a:var']) + call RunDbgCmd(buf, 'step', ['line 2: let var2 = Bazz(var1) + 4']) + call RunDbgCmd(buf, 'step', ['line 1: try']) + call RunDbgCmd(buf, 'step', ['line 2: let var1 = 3 + a:var']) + call RunDbgCmd(buf, 'step', ['line 3: let var3 = "another var"']) " check backtrace call RunDbgCmd(buf, 'backtrace', [ -- cgit