1*******************************************************************************
2*******************************************************************************
3*******************************************************************************
4*******************************************************************************
5*******************************************************************************
6
7
8HEY THIS TEST IS FAILING AND I DONT KNOW HOW TO REPRODUCE IT??
9
10At the point when this file was authored, I had no idea how to get the crash
11artifacts out of bazel/the fuzzer/kokoro/somewhere and onto your machine.
12
13Without that this seemed like a problem - why check whether fuzzers pass if
14we can't debug them?
15
16My thinking is this: if we can find an example that fails within a few minutes
17in CI, we can probably do likewise on your machine.
18
19Try:
20
21bazel build path/to/fuzzer --config=fuzzer_asan -c dbg
22bazel-bin/path/to/fuzzer path/to/fuzzer_corpus -jobs=$CPUS -workers=$CPUS
23
24You should see whatever failure this CI job found before terribly long.
25
26
27*******************************************************************************
28*******************************************************************************
29*******************************************************************************
30*******************************************************************************
31*******************************************************************************
32