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
This commit is contained in:
Paul Gschwendtner 2019-02-06 17:52:35 +01:00 committed by Miško Hevery
parent fb9a4a668c
commit fed8c1d160
1 changed files with 2 additions and 2 deletions

View File

@ -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'],