pkg/bisect: estimate confidence in the result

Estimate reproducer's flakiness more carefully, as it can help us get
better results.

During config minimization, do not let reproducibility drop too low.

For each test() run, estimate our confidence in the result. For now,
only consider the false negative case: if we got no crashes, it's likely
that the bug is there, but the reproducer was not lucky enough. Given an
estimate of reproduction likelihood, we can easily calculate the chance
of an invalid result: (1-probability)^runs.

Combine all individual test() confidences into Result.Confidence. If the
resulting Confidence is too low, ignore the bisection result.

0 files changed, 0 insertions, 0 deletions