[libFuzzer] Split fuzzer-jobs for different platforms.

[mpividori]

Summary

I add fuzzer-jobs-win.test for Windows.

[kcc]

This is too much -- having such large windows-only tests will make maintenance more costly for me.
Until someone promises to keep maintaining the windows port after your internship is over I don't want to accept such win-only tests.
(Even then, I'd prefer to keep things in a single test, whenever possible)

[mpividori]

Ok, I can simply abandon this diff.

lib/Fuzzer/test/fuzzer-jobs-win.test

+REQUIRES: windows
+
+RUN: rm -rf %tmp
+RUN: mkdir %tmp && cd %tmp
+# Create a shared corpus directory
+RUN: rm -rf FuzzerJobsTestCORPUS
+RUN: mkdir FuzzerJobsTestCORPUS
+RUN: rm -f fuzz-{0,1}.log
+# Start fuzzer and in parallel check that the output files
+# that should be created exist.
+RUN: cmd /c "start /b LLVMFuzzer-EmptyTest -max_total_time=4 -jobs=2 -workers=2 FuzzerJobsTestCORPUS > %t-fuzzer-jobs-test.log 2>&1 && \
+# Wait a short while to give time for the child processes
+# to start fuzzing
+RUN: sleep 2 && \
+# If the instances are running in parallel they should have created their log
+# files by now.
+RUN: ls fuzz-0.log && \
+RUN: ls fuzz-1.log && \
+# Check if libFuzzer is still running.
+RUN: tasklist | grep LLVMFuzzer-EmptyTest"
+
+RUN: rm -f fuzz-{0,1}.log
+RUN: rm -rf FuzzerJobsTestCORPUS
+RUN: FileCheck -input-file=%t-fuzzer-jobs-test.log %s
+RUN: rm %t-fuzzer-jobs-test.log
+
+CHECK-DAG: Job 0 exited with exit code 0
+CHECK-DAG: Job 1 exited with exit code 0