view src/testdir/test_vim9_fails.vim @ 29734:2d2f36e430f9 v9.0.0207

patch 9.0.0207: stacktrace not shown when debugging Commit: https://github.com/vim/vim/commit/28c162f6f1f525882a9a60f10ab4836dee7eb59f Author: zeertzjq <zeertzjq@outlook.com> Date: Sun Aug 14 14:49:50 2022 +0100 patch 9.0.0207: stacktrace not shown when debugging Problem: Stacktrace not shown when debugging. Solution: Set msg_scroll in msg_source(). (closes https://github.com/vim/vim/issues/10917)
author Bram Moolenaar <Bram@vim.org>
date Sun, 14 Aug 2022 16:00:03 +0200
parents b94ef0b282f1
children 54e36d01847b
line wrap: on
line source

" Test for Vim9 script with failures, causing memory leaks to be reported.
" The leaks happen after a fork() and can be ignored.

source check.vim

def Test_assignment()
  if !has('channel')
    CheckFeature channel
  else
    var chan1: channel
    var job1: job
    var job2: job = job_start('willfail')
  endif
enddef

" Unclear why this test causes valgrind to report problems.
def Test_job_info_return_type()
  if !has('job')
    CheckFeature job
  else
    var job: job = job_start(&shell)
    var jobs = job_info()
    assert_equal('list<job>', typename(jobs))
    assert_equal('dict<any>', typename(job_info(jobs[0])))
    job_stop(job)
  endif
enddef