• Mythri's avatar
    Fix JSTest/Proxies/Set.*Trap tests to return true from the trap · 58ebbf34
    Mythri authored
    The spec specifies that a non-true return values from the trap functions
    should be treated as error in the strict mode. With the new lazy feedback
    effort inferring the language mode is expensive and causes regression on
    these tests. Since the test doesn't actually need to test this, fixing
    them to return true would help test the performance of calling the trap
    without the unnecessary overhead of inferring the language mode.
    
    Bug: chromium:925289
    Change-Id: Ib650c3210ee260296257ae3b56174099a5492675
    Reviewed-on: https://chromium-review.googlesource.com/c/1462959
    Commit-Queue: Mythri Alle <mythria@chromium.org>
    Reviewed-by: 's avatarMaya Lekova <mslekova@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#59505}
    58ebbf34
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
common Loading commit data...
debugger Loading commit data...
fuzzer Loading commit data...
inspector 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...
mkgrokdump Loading commit data...
mozilla Loading commit data...
preparser Loading commit data...
test262 Loading commit data...
torque Loading commit data...
unittests Loading commit data...
wasm-js Loading commit data...
wasm-spec-tests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...