• Jakob Kummerow's avatar
    [cctest] Make sure FLAG_stack_size settings have effect · a43f3818
    Jakob Kummerow authored
    Using the default cctest TEST(...) macro causes later writes to
    FLAG_stack_size to have no effect, because the StackGuard reads
    that flag's value during Isolate initialization, which is done
    before the test body is executed. This patch changes the two
    existing tests that accidentally did this to UNINITIALIZED_TEST,
    putting them in charge of Isolate creation, thereby ensuring that
    the intended stack size is configured correctly.
    
    Change-Id: Ib030795ef46f23d576f6dbbd26b347ac804b5085
    Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2862778Reviewed-by: 's avatarYang Guo <yangguo@chromium.org>
    Commit-Queue: Yang Guo <yangguo@chromium.org>
    Auto-Submit: Jakob Kummerow <jkummerow@chromium.org>
    Cr-Commit-Position: refs/heads/master@{#74309}
    a43f3818
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...
fuzzilli 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...