Mercurial > vim
view src/testdir/test_job_fails.vim @ 10627:fb9c28aca006 v8.0.0203
patch 8.0.0203: order of complication flags is sometimes wrong
commit https://github.com/vim/vim/commit/6e78e27b8aace2e4c2412bfc4de6567509258d28
Author: Bram Moolenaar <Bram@vim.org>
Date: Tue Jan 17 19:20:15 2017 +0100
patch 8.0.0203: order of complication flags is sometimes wrong
Problem: Order of complication flags is sometimes wrong.
Solution: Put interface-specific flags before ALL_CFLAGS. (idea by Yousong
Zhou, closes #1100)
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Tue, 17 Jan 2017 19:30:04 +0100 |
parents | e0b783389bea |
children | c1347c968d31 |
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 g:job = job_start('axdfxsdf') if has('unix') call WaitFor('job_status(g:job) == "dead"') call assert_equal('dead', job_status(g:job)) else call WaitFor('job_status(g:job) == "fail"') call assert_equal('fail', job_status(g:job)) endif unlet g:job endif endfunc