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.
diff --git a/src/testdir/test_job_fails.vim b/src/testdir/test_job_fails.vim
new file mode 100644
index 0000000..ddab6a3
--- /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