Mercurial > vim

view src/testdir/test_job_fails.vim @ 22067:59984404e520 v8.2.1583

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
patch 8.2.1583: MS-Windows: cannot easily measure code coverage Commit: https://github.com/vim/vim/commit/18eedfa40b45b1de955d61417e9918ef7d6e83f9 Author: Bram Moolenaar <Bram@vim.org> Date: Thu Sep 3 19:50:05 2020 +0200 patch 8.2.1583: MS-Windows: cannot easily measure code coverage Problem: MS-Windows: cannot easily measure code coverage. Solution: Add the COVERAGE option. (Ken Takata, closes https://github.com/vim/vim/issues/6842)
author Bram Moolenaar <Bram@vim.org>
date Thu, 03 Sep 2020 20:00:03 +0200
parents 08940efa6b4e
children
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 exits right away it's not a real leak.

source check.vim

func Test_job_start_fails()
  CheckFeature 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
endfunc

" vim: shiftwidth=2 sts=2 expandtab