Mercurial > vim
view src/testdir/test_job_fails.vim @ 23596:9fa72351c18f v8.2.2340
patch 8.2.2340: win_execute() unexpectedly returns number zero when failing
Commit: https://github.com/vim/vim/commit/37487e16da7877129edee8d11b9b7f5c8df312c6
Author: Bram Moolenaar <Bram@vim.org>
Date: Tue Jan 12 22:08:53 2021 +0100
patch 8.2.2340: win_execute() unexpectedly returns number zero when failing
Problem: win_execute() unexpectedly returns number zero when failing.
Solution: Return an empty string. (closes https://github.com/vim/vim/issues/7665)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Tue, 12 Jan 2021 22:15:03 +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