Revert "[code coverage] Run corpus in parallel for fuzzer targets."
This reverts commit 52b92eee57d9ada32f4aa75c0915a53043dfd032.
Reason for revert: This doesn't help. We should run fuzzer on Swarming instead.
Original change's description:
> [code coverage] Run corpus in parallel for fuzzer targets.
>
> Since fuzzer itself can't support executing corpus in parallel yet, we enable
> this by running multiple instances of the fuzzer against sharded corpus.
> The long term solution is still for fuzzer itself to support this.
>
> Bug: 915480
> Change-Id: Ibc73efcc97bd9d515b4d6a00e905ec1b5496b9b8
> Reviewed-on: https://chromium-review.googlesource.com/c/1379389
> Reviewed-by: Yuke Liao <liaoyuke@chromium.org>
> Reviewed-by: Jonathan Metzman <metzman@chromium.org>
> Commit-Queue: Shuotao Gao <stgao@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#617220}
TBR=stgao@chromium.org,mmoroz@chromium.org,liaoyuke@chromium.org,metzman@chromium.org
Change-Id: I999bb2c536f03a5d4c03fcf8eb1c2c984bd9aff8
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 915480
Reviewed-on: https://chromium-review.googlesource.com/c/1383194
Reviewed-by: Shuotao Gao <stgao@chromium.org>
Commit-Queue: Shuotao Gao <stgao@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#617600}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 1224668f12fd922f4057d6695c229600427f58821 file changed
