Mercurial > vim

view src/testdir/test_job_fails.vim @ 23782:82a8abc75070 v8.2.2432

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
patch 8.2.2432: libvterm tests are executed even when libtool doesn't work Commit: https://github.com/vim/vim/commit/76ab5446d530a1c81ead0ee42cb55b4a4d515bad Author: Bram Moolenaar <Bram@vim.org> Date: Sat Jan 30 20:35:28 2021 +0100 patch 8.2.2432: libvterm tests are executed even when libtool doesn't work Problem: Libvterm tests are executed even when libtool doesn't work. Solution: Only run libvterm tests if /usr/bin/gcc exists.
author Bram Moolenaar <Bram@vim.org>
date Sat, 30 Jan 2021 20:45:04 +0100
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