Mercurial > vim
view src/testdir/test_job_fails.vim @ 16192:1ab0d1f7807a v8.1.1101
patch 8.1.1101: signals test may fail in the GUI
commit https://github.com/vim/vim/commit/690a905a0199f5ff733e5a12be9ba94ae6043ef4
Author: Bram Moolenaar <Bram@vim.org>
Date: Tue Apr 2 21:45:41 2019 +0200
patch 8.1.1101: signals test may fail in the GUI
Problem: Signals test may fail in the GUI.
Solution: Skip the test for the GUI. (Yee Checng Chin, closes https://github.com/vim/vim/issues/4202)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Tue, 02 Apr 2019 22:00: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