Mercurial > vim
comparison src/testdir/test_job_fails.vim @ 9764:e0b783389bea v7.4.2157
commit https://github.com/vim/vim/commit/46c4d4ac66aa2b129f4dcec9debfda606f72d4b3
Author: Bram Moolenaar <Bram@vim.org>
Date: Fri Aug 5 19:31:57 2016 +0200
patch 7.4.2157
Problem: Test_job_start_fails() is expected to report memory leaks, making
it hard to see other leaks in test_partial.
Solution: Move Test_job_start_fails() to a separate test file.
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Fri, 05 Aug 2016 19:45:05 +0200 |
parents | |
children | c1347c968d31 |
comparison
equal
deleted
inserted
replaced
9763:7fba2e73bc86 | 9764:e0b783389bea |
---|---|
1 " This test is in a separate file, because it usually causes reports for memory | |
2 " leaks under valgrind. That is because when fork/exec fails memory is not | |
3 " freed. Since the process exists right away it's not a real leak. | |
4 | |
5 source shared.vim | |
6 | |
7 func Test_job_start_fails() | |
8 if has('job') | |
9 let g:job = job_start('axdfxsdf') | |
10 if has('unix') | |
11 call WaitFor('job_status(g:job) == "dead"') | |
12 call assert_equal('dead', job_status(g:job)) | |
13 else | |
14 call WaitFor('job_status(g:job) == "fail"') | |
15 call assert_equal('fail', job_status(g:job)) | |
16 endif | |
17 unlet g:job | |
18 endif | |
19 endfunc |