Jon Ross-PerkinsandAdrien Leravat 16f86471e7 Shard the explorer fuzzer test (#2642) ...

Right now //explorer/fuzzing:explorer_fuzzer takes my machine 80s to run, just because of the corpus size. The corpus is actually pretty small compared to the toolchain fuzzer, so reducing the corpus size doesn't feel quite right.

This adds support for sharding fuzz tests, and with 8 shards each is closer to 10s. This should put it closer to the noise of other explorer tests in terms of runtime.

Unfortunately I'm not seeing a sharding flag in the llvm library, which seems fair. However, that's why I'm working around it by creating separate test targets per shard, then a suite to merge them back together. The use of `shard_count` for this is idiomatic for bazel rules; I'm using it so that switching implementations should be low-impact if that's ever needed.

Co-authored-by: Adrien Leravat <Pixep@users.noreply.github.com>

2023-03-01 11:22:33 -08:00

..

BUILD

Merge LLVM and Bazel infra from the toolchain repository. (#207)

2020-12-04 19:26:07 -08:00

rules.bzl

Shard the explorer fuzzer test (#2642)

2023-03-01 11:22:33 -08:00