From fed8c1d160cc71f08c61ff60bc2e768a59229bc1 Mon Sep 17 00:00:00 2001 From: Paul Gschwendtner Date: Wed, 6 Feb 2019 17:52:35 +0100 Subject: [PATCH] build: unable to run perf bazel e2e tests on windows (#28568) Currently it's not possible to run the benchmark e2e tests with Bazel on Windows because the logic that imports the `perf_util`'s is not using a proper Bazel script manifest path. A script manifest path should not start with `./angular/`, but rather with the workspace name (which is in our case `angular/`) PR Close #28568 --- protractor-perf.conf.js | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/protractor-perf.conf.js b/protractor-perf.conf.js index da4054d91c..702b360861 100644 --- a/protractor-perf.conf.js +++ b/protractor-perf.conf.js @@ -14,8 +14,8 @@ const isBazel = !!process.env.RUNFILES; // Make sure that the command line is read as the first thing // as this could exit node if the help script should be printed. -const BASE = isBazel ? 'angular/modules' : 'dist/all'; -require(`./${BASE}/e2e_util/perf_util`).readCommandLine(); +const BASE = isBazel ? 'angular/modules' : './dist/all'; +require(`${BASE}/e2e_util/perf_util`).readCommandLine(); const CHROME_OPTIONS = { 'args': ['--js-flags=--expose-gc', '--no-sandbox', '--headless', '--disable-dev-shm-usage'],