Mercurial > vim

view src/testdir/test_job_fails.vim @ 9764:e0b783389bea v7.4.2157

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
commit https://github.com/vim/vim/commit/46c4d4ac66aa2b129f4dcec9debfda606f72d4b3 Author: Bram Moolenaar <Bram@vim.org> Date: Fri Aug 5 19:31:57 2016 +0200 patch 7.4.2157 Problem: Test_job_start_fails() is expected to report memory leaks, making it hard to see other leaks in test_partial. Solution: Move Test_job_start_fails() to a separate test file.
author Christian Brabandt <cb@256bit.org>
date Fri, 05 Aug 2016 19:45:05 +0200
parents
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