Minimizing timeout test cases

[szhorvat]

In my experience, test cases for timeouts are not minimized. I'm not sure if this is intentional, or a failure of the system to do the minimization. When triggering minimization manually, I get "Minimize task errored out: LibFuzzer minimization failed.". Given how painful it is to minimize these locally, it would be very useful to support this, including setting a reasonable timeout value.

In many cases, timeouts relate directly to the size of the input. In igraph, we encountered cases where it's the specific structure of the input was to blame. Obtaining a small test case is usually necessary to debug these.

[maflcko]

including setting a reasonable timeout value.

I think this is already possible, though I haven't tried it. See for example https://github.com/google/oss-fuzz/blob/master/projects/json/fuzzer-parse.options#L3 . (However, max_len should be done inside the fuzz target code itself, see #5408)

[szhorvat]

What I am looking for is to set a lower timeout just for the sake of minimization, not to get a global timeout for all fuzzing. Actually, I am just looking for way to help the minimizer succeed on OSS-Fuzz, so I wouldn't have to do it locally.