• Leszek Swirski's avatar
    [test] Create one Isolate per unit test (not test suite) · 0c2530ff
    Leszek Swirski authored
    Change the unittests Isolate mixin to create one Isolate per test,
    rather than one per test suite. We usually run these tests independently
    in separate processes anyway, so this shouldn't affect normal test
    execution, but it will avoid Isolate state leaking across tests when
    running the unittests binary directly.
    
    Take this opportunity to also clean up the mixins, changing counter
    initialization and forcing pointer compression into template traits.
    
    Bug: v8:10142
    Change-Id: If92046f9c6f2056252d099faed04d97844ef7319
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2143818Reviewed-by: 's avatarIgor Sheludko <ishell@chromium.org>
    Commit-Queue: Leszek Swirski <leszeks@chromium.org>
    Auto-Submit: Leszek Swirski <leszeks@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#67110}
    0c2530ff
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
common Loading commit data...
debugger Loading commit data...
debugging 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...
test262 Loading commit data...
torque Loading commit data...
unittests Loading commit data...
wasm-api-tests Loading commit data...
wasm-js Loading commit data...
wasm-spec-tests Loading commit data...
webkit Loading commit data...
BUILD.gn Loading commit data...
OWNERS Loading commit data...