diff options
| author | Aleksandr Nogikh <nogikh@google.com> | 2025-06-23 15:27:39 +0200 |
|---|---|---|
| committer | Aleksandr Nogikh <nogikh@google.com> | 2025-06-26 12:49:47 +0000 |
| commit | c3f8bb06ed4d6ad6211729efcd0d5aa4a26d5c4d (patch) | |
| tree | f6f96131b5eb73e696dd87cf812b5756e556d106 /executor/embed.go | |
| parent | 5fd74b4cc1dd3fa8867f53dbbb67c950188250de (diff) | |
pkg/repro: validate the result
The whole pkg/repro algorithm is very sensitive to random kernel
crashes, yet all other parts of the system rely on pkg/repro reproducers
being reliable enough to draw meaningful conclusions from running them.
A single unrelated kernel crash during repro extraction may divert the
whole process since all the checks we do during the process (e.g. during
minimization or when we drop prog opts) assume that if the kernel didn't
crash, it was due to the fact that the removed part was essential for
reproduction, and not due to the fact that our reproducer is already
broken.
Since such problem may happen at any moment, let's do a single
validation check at the very end of repro generation. Overall, these
cases are not super frequent, so it's not worth it to re-check every
step.
Calculate the reliability score of thre reproducer and use a 15% default
cut-off for flaky results.
Diffstat (limited to 'executor/embed.go')
0 files changed, 0 insertions, 0 deletions
