diff options
| author | Bram Moolenaar <Bram@vim.org> | 2016-08-05 19:31:57 +0200 |
|---|---|---|
| committer | Bram Moolenaar <Bram@vim.org> | 2016-08-05 19:31:57 +0200 |
| commit | 46c4d4ac66aa2b129f4dcec9debfda606f72d4b3 (patch) | |
| tree | 74cf9fd7b6f20f4873049fc6bbb2e1e5104d2628 /src/testdir/test_job_fails.vim | |
| parent | c90f2aedd0a5dc2cc75bc9b5f475f8a3e3fe36b1 (diff) | |
| download | vim-git-46c4d4ac66aa2b129f4dcec9debfda606f72d4b3.tar.gz | |
patch 7.4.2157v7.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.
Diffstat (limited to 'src/testdir/test_job_fails.vim')
| -rw-r--r-- | src/testdir/test_job_fails.vim | 19 |
1 files changed, 19 insertions, 0 deletions
diff --git a/src/testdir/test_job_fails.vim b/src/testdir/test_job_fails.vim new file mode 100644 index 000000000..ddab6a316 --- /dev/null +++ b/src/testdir/test_job_fails.vim @@ -0,0 +1,19 @@ +" 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 |