view src/testdir/test_job_fails.vim @ 34755:1a411f737239 v9.1.0255

patch 9.1.0255: Vim9: no indication of script nr in stack trace of classes Commit: https://github.com/vim/vim/commit/16cdfa69e07190674a8e85a48144a467472ca2f4 Author: Ernie Rael <errael@raelity.com> Date: Tue Apr 2 19:05:39 2024 +0200 patch 9.1.0255: Vim9: no indication of script nr in stack trace of classes Problem: Vim9: no indication of script nr in stack trace of classes Solution: Prefix the class name with the script name in the stack trace. (Ernie Rael) fixes: #14376 closes: #14390 Signed-off-by: Ernie Rael <errael@raelity.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
author Christian Brabandt <cb@256bit.org>
date Tue, 02 Apr 2024 19:15:04 +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