Skip to content

Commit 5593b32

Browse files
authored
Fuzzer: Fix Merge fuzzing when input must be ignored (#7866)
I saw a failure where the second module hit a VM limit, so it should be ignored, but we weren't, and ended up thinking it behaved differently after merge.
1 parent 4d07c73 commit 5593b32

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

scripts/fuzz_opt.py

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1485,11 +1485,17 @@ def handle(self, wasm):
14851485

14861486
# verify that merging in the second module did not alter the output.
14871487
output = run_bynterp(wasm, ['--fuzz-exec-before', '-all'])
1488+
if output == IGNORE:
1489+
return
14881490
output = fix_output(output)
14891491
second_output = run_bynterp(second_wasm, ['--fuzz-exec-before', '-all'])
14901492
second_output = fix_output(second_output)
1493+
if second_output == IGNORE:
1494+
return
14911495
merged_output = run_bynterp(merged, ['--fuzz-exec-before', '-all'])
14921496
merged_output = fix_output(merged_output)
1497+
if merged_output == IGNORE:
1498+
return
14931499

14941500
# If the second module traps in instantiation, then the merged module
14951501
# must do so as well, regardless of what the first module does. (In

0 commit comments

Comments
 (0)