Mercurial > vim

view src/testdir/test_job_fails.vim @ 12269:d2373927d76d v8.0.1014

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
patch 8.0.1014: old compiler doesn't know uint32_t commit https://github.com/vim/vim/commit/b47a2597e64b4c4f728433ae005cf6ff1d0dd5c1 Author: Bram Moolenaar <Bram@vim.org> Date: Wed Aug 30 13:22:28 2017 +0200 patch 8.0.1014: old compiler doesn't know uint32_t Problem: Old compiler doesn't know uint32_t. Warning for using NULL instead of NUL. Solution: Use UINT32_T. Use NUL instead of NULL.
author Christian Brabandt <cb@256bit.org>
date Wed, 30 Aug 2017 13:30:04 +0200
parents e0b783389bea
children c1347c968d31
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 g:job = job_start('axdfxsdf')
    if has('unix')
      call WaitFor('job_status(g:job) == "dead"')
      call assert_equal('dead', job_status(g:job))
    else
      call WaitFor('job_status(g:job) == "fail"')
      call assert_equal('fail', job_status(g:job))
    endif
    unlet g:job
  endif
endfunc