iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

build: disable sandbox when running protractor through bazel (#28557) 

Adds `--no-sandbox` in order to disable the sandbox when running Protractor through Bazel. Enabling the sandbox causes Chrome to crash under certain environments.

PR Close #28557
This commit is contained in:
Kristiyan Kostadinov 2019-02-06 10:48:23 +01:00 committed by Misko Hevery
parent 851cf16134
commit 8d90142a0f
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
packages/bazel/src/protractor/protractor.conf.js
View File

@ -129,10 +129,12 @@ if (process.env['WEB_TEST_METADATA']) {
if (webTestNamedFiles['CHROMIUM']) {
const chromeBin = require.resolve(webTestNamedFiles['CHROMIUM']);
const chromeDriver = require.resolve(webTestNamedFiles['CHROMEDRIVER']);
const args = [];
// The sandbox needs to be disabled, because it causes Chrome to crash on some environments.
// See: http://chromedriver.chromium.org/help/chrome-doesn-t-start
const args = ['--no-sandbox'];
if (headless) {
args.push('--headless');
args.push('--disable-gpu');
args.push('--headless', '--disable-gpu');
}
setConf(conf, 'directConnect', true, 'is set to true for chrome');
setConf(conf, 'chromeDriver', chromeDriver, 'is determined by the browsers attribute');