From 8ef940b2053776168da7c1a36a1322e347a3435f Mon Sep 17 00:00:00 2001 From: Greg Magolan Date: Thu, 16 Apr 2020 15:17:06 -0700 Subject: [PATCH] build: use no-remote-exec tag so test still runs in sandbox Turns out there is a linker bug with no sandbox. --- packages/angular_devkit/build_angular/BUILD.bazel | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/packages/angular_devkit/build_angular/BUILD.bazel b/packages/angular_devkit/build_angular/BUILD.bazel index 2ed447d0cc..9128dce297 100644 --- a/packages/angular_devkit/build_angular/BUILD.bazel +++ b/packages/angular_devkit/build_angular/BUILD.bazel @@ -261,8 +261,8 @@ LARGE_SPECS = { "@npm//puppeteer", "@npm//ts-node", ], - # NB: must be run locally because webdriver manager uses an absolute path to chromedriver - "tags": ["local"], + # NB: does not run on rbe because webdriver manager uses an absolute path to chromedriver + "tags": ["no-remote-exec"], }, "dev-server": { "extra_deps": [ @@ -290,8 +290,8 @@ LARGE_SPECS = { "@npm//puppeteer", "@npm//ts-node", ], - # NB: must be run locally because webdriver manager uses an absolute path to chromedriver - "tags": ["local"], + # NB: does not run on rbe because webdriver manager uses an absolute path to chromedriver + "tags": ["no-remote-exec"], # NB: multiple shards will compete for port 4200 so limiting to 1 "shards": 1, },