Status: Available
Owner: ----
CC: mache...@
chromium.org,
sa...@chromium.org Components: Infrastructure Sandbox
Type: FeatureRequest
New issue 13058 by
sa...@chromium.org: Enable the V8 Sandbox on V8 bots
https://bugs.chromium.org/p/v8/issues/detail?id=13058The V8 sandbox (
go/ubercage) is enabled by default in Chromium. To test and benchmark the configuration of V8 that ships in Chromium, and to avoid breakages during V8 -> Chromium rolls, we should also enable the V8 sandbox (gn arg `v8_enable_sandbox = true`) on as many V8 bots as possible. However, we should also test the non-sandbox configuration. In particular:
- x64 (and I guess arm64?) V8 CI, Try and perf bots should all enable it
- No changes to Chromium bots are necessary as the sandbox is automatically enabled when building with Chromium
- Non-Chromium embedder bots (Node.js, Bazel, ...) should keep using the default configuration (i.e. sandbox off)
- There should be a new set of x64 release and debug bot with one trybot in CQ with the sandbox explicitly disabled (`v8_enable_sandbox = false`)
- The multiarch build of the correctness fuzzer (see
https://source.chromium.org/chromium/chromium/src/+/main:v8/BUILD.gn;l=471) should include it as well
--
You received this message because:
1. The project was configured to send all issue notifications to this address
You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings