• gdeepti's avatar
    [wasm] Fix test-run-wasm-module tests in debug mode. · dd3b14b7
    gdeepti authored
    test-run-wasm-module cctests broken in debug since recent refactoring changes for moving Compilation/Instantiation off the module object (https://codereview.chromium.org/2320723005). The problem here is that SetupIsolateForWasm tries to add the same property to a module_object multiple times and hits a DCHECK when this property is found on a lookup.
     - Fixed to use the setup method only once when CcTest::InitIsolateOnce is used.
     - Move setup method to test as this is only used for cctests/fuzzers. The install method should take care of this in the regular JS pipeline.
    
     R=mtrofin@chromium.org, ahaas@chromium.org
    
    Review-Url: https://codereview.chromium.org/2342263002
    Cr-Commit-Position: refs/heads/master@{#39484}
    dd3b14b7
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
common Loading commit data...
fuzzer Loading commit data...
inspector_protocol_parser_test Loading commit data...
intl Loading commit data...
js-perf-test Loading commit data...
memory Loading commit data...
message Loading commit data...
mjsunit Loading commit data...
mozilla Loading commit data...
preparser Loading commit data...
promises-aplus Loading commit data...
simdjs Loading commit data...
test262 Loading commit data...
unittests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...
bot_default.gyp Loading commit data...
bot_default.isolate Loading commit data...
default.gyp Loading commit data...
default.isolate Loading commit data...
optimize_for_size.gyp Loading commit data...
optimize_for_size.isolate Loading commit data...
perf.gyp Loading commit data...
perf.isolate Loading commit data...