6ec763657a
Page allocation in a partially-reserved sandbox is generally best-effort once the reserved part is fully allocated, which happens in this test. As such, there is no guarantee that this test succeeds, and it does seem to fail in practice on some bots with memory sanitizers enabled. The same logic is essentially tested by the VirtualAddressSpaceTest.TestEmulatedSubspace test so simply deleting this test should be fine. Bug: v8:13040 Change-Id: I1469bd9d2e330a6e834bb565ce4e7f5985be28a9 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3749180 Reviewed-by: Tobias Tebbi <tebbi@chromium.org> Commit-Queue: Tobias Tebbi <tebbi@chromium.org> Auto-Submit: Samuel Groß <saelo@chromium.org> Cr-Commit-Position: refs/heads/main@{#81578} |
||
---|---|---|
.. | ||
benchmarks | ||
bigint | ||
cctest | ||
common | ||
debugger | ||
debugging | ||
fuzzer | ||
fuzzilli | ||
inspector | ||
intl | ||
js-perf-test | ||
memory | ||
message | ||
mjsunit | ||
mkgrokdump | ||
mozilla | ||
test262 | ||
torque | ||
unittests | ||
wasm-api-tests | ||
wasm-js | ||
wasm-spec-tests | ||
webkit | ||
BUILD.gn | ||
OWNERS |