The two frameworks num_fuzzer and standard_runner tweak testing
behavior slightly, which can cause problems when flake bisect runs
for cases detected with num_fuzzer. Flake bisect is only implemented
for the standard runner.
The differences are:
- Numfuzz uses a few more extra default flags.
- Numfuzz uses an additional test processor that ignores timeouts
and expected failures.
- Numfuzz passes an extra file in the Mjsunit test suite.
This change enables running the standard runner with this specific
numfuzz behavior, which makes flake bisect the same way as the
original run. The --framework cmd-line flag needs to be passed.
On the infra side, the framework name is already available for
failures. In a follow up, we'll pass it as a cmd-line in fitting
revisions during flake bisect.
Bug: 42202137
Change-Id: I77703ba2c7f2ee345f2af2925370da14f3149ac6
Cq-Include-Trybots: luci.v8.try:v8_numfuzz_dbg,v8_numfuzz_tsan_rel
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6063807
Reviewed-by: Alexander Schulze <alexschulze@chromium.org>
Commit-Queue: Michael Achenbach <machenbach@chromium.org>
Cr-Commit-Position: refs/heads/main@{#97616}
Michael Achenbach
2fb66710af