Benchmarks sometimes get stuck

[konsumlamm]

I unfortunately don't have a reproducible example, as this doesn't happen deterministically, but sometimes the benchmarks seem to get stuck. Restarting the benchmarks usually fixes the problem.

[Bodigrim]

And no suggestions to set -t100in stderr? You might try setting debug build flag.

[konsumlamm]

Eventually, I get

This benchmark takes more than 100 seconds. Consider setting --timeout, if this is unexpected (or to silence this warning).

Is this to be expected? The benchmarks shouldn't vary too much and when rerunning, it doesn't occur, so this feels like some bug.

[Bodigrim]

This is expected, either set --timeout 100, or alternatively increase --stdev.