view src/testdir/test_job_fails.vim @ 13892:eadecbe4e390 v8.0.1817

patch 8.0.1817: a timer may change v:count unexpectedly commit https://github.com/vim/vim/commit/b0f42ba60d9e6d101d103421ba0c351811615c15 Author: Bram Moolenaar <Bram@vim.org> Date: Sat May 12 15:38:26 2018 +0200 patch 8.0.1817: a timer may change v:count unexpectedly Problem: A timer may change v:count unexpectedly. Solution: Save and restore v:count and similar variables when a timer callback is invoked. (closes #2897)
author Christian Brabandt <cb@256bit.org>
date Sat, 12 May 2018 15:45:05 +0200
parents 415185e2c970
children b3e93a05c3ca
line wrap: on
line source

" This test is in a separate file, because it usually causes reports for memory
" leaks under valgrind.  That is because when fork/exec fails memory is not
" freed.  Since the process exists right away it's not a real leak.

source shared.vim

func Test_job_start_fails()
  if has('job')
    let job = job_start('axdfxsdf')
    if has('unix')
      call WaitForAssert({-> assert_equal("dead", job_status(job))})
    else
      call WaitForAssert({-> assert_equal("fail", job_status(job))})
    endif
  endif
endfunc