
This target fails with odd error that we need to investigate: [01:19:32] I/direct - Using ChromeDriver directly... [01:19:32] E/direct - Error code: 135 [01:19:32] E/direct - Error message: Could not find chromedriver at /home/circleci/.cache/bazel/_bazel_circleci/9ce5c2144ecf75d11717c0aa41e45a8d/external/ngdeps/node_modules/webdriver-manager/selenium/chromedriver_2.41. Run 'webdriver-manager update' to download binaries. [01:19:32] E/direct - Error: Could not find chromedriver at /home/circleci/.cache/bazel/_bazel_circleci/9ce5c2144ecf75d11717c0aa41e45a8d/external/ngdeps/node_modules/webdriver-manager/selenium/chromedriver_2.41. Run 'webdriver-manager update' to download binaries. PR Close #26735
Benchmark Directory Layout
Bazel
Under bazel the rules for laying out test files are slightly different. Use largetable/render3
as an example.
Put the perf file in current subdirectory (ie largetable
) such that the same perf file can be used for each of the sub-subdirectories. (ie largetable/*
should all be testable with the same perf file largetable/largetable_perf.spec.ts
). Under bazel, typescript protractor spec files must end with .spec.ts
or .test.ts
.