Mercurial > vim
view src/testdir/test_job_fails.vim @ 17249:3e2e998ce0db v8.1.1624
patch 8.1.1624: when testing in the GUI may try to run gvim in a terminal
commit https://github.com/vim/vim/commit/0d702028feb859e6bde9a0c943d398d86294beb7
Author: Bram Moolenaar <Bram@vim.org>
Date: Thu Jul 4 14:20:41 2019 +0200
patch 8.1.1624: when testing in the GUI may try to run gvim in a terminal
Problem: When testing in the GUI may try to run gvim in a terminal.
Solution: Add the -v argument. (Yee Cheng Chin, closes https://github.com/vim/vim/issues/4605) Don't skip
tests that work now.
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Thu, 04 Jul 2019 14:30:05 +0200 |
parents | 415185e2c970 |
children | b3e93a05c3ca |
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 exists right away it's not a real leak. source shared.vim func Test_job_start_fails() if has('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 endif endfunc