forked from kozorizki/binaryen
d808e900b8
The risk the warning checks for is giving the reducer a script that ignores the input. To do so it runs the command in the input, and runs it on a garbage file, and checks if the result is different. However, if the script does immediately fail on the input - because the input is a crash testcase or such - then this does not work, as the result on a garbage input may be the same error. To avoid that, also check what happens on a trivial valid wasm as input. Only show the warning if the result on the original input, on a garbage wasm, and on a trivial wasm, are all the same - in that case, likely the script really is ignoring the input.
14 lines
748 B
Python
14 lines
748 B
Python
import subprocess
|
|
|
|
from scripts.test import shared
|
|
from . import utils
|
|
|
|
|
|
class ReduceTest(utils.BinaryenTestCase):
|
|
def test_warn_on_no_passes(self):
|
|
# run a reducer command that does nothing, and so ignores the input
|
|
open('do_nothing.py', 'w').close()
|
|
cmd = shared.WASM_REDUCE + [self.input_path('empty.wasm'), '-w', 'w.wasm', '-t', 't.wasm', '--command=python do_nothing.py']
|
|
err = shared.run_process(cmd, check=False, stderr=subprocess.PIPE).stderr
|
|
self.assertIn('Fatal: running the command on the given input gives the same result as when running it on either a trivial valid wasm or a file with nonsense in it. does the script not look at the test file (t.wasm)? (use -f to ignore this check)', err)
|