The components repository has a Yarn resolution to ensure that dgeni-packages uses a specific TypeScript version. This resolution causes the specified TS version to be considered as candidate for the `@angular/bazel` peer dependency. Ultimately, Yarn decides to use the TypeScript version from the resolution for `@angular/bazel`, and builds will fail due to a version mismatch. This is because `tsickle` will use the hoisted top-level TS version (set to `3.7.4` ), while `@angular/bazel` uses the version from the resolution (at the time of writing: v3.6.4) PR Close #33717
22 lines
968 B
Bash
Executable File
22 lines
968 B
Bash
Executable File
#!/usr/bin/env bash
|
|
set -u -e -o pipefail
|
|
|
|
# This script runs unit tests from angular/material2.
|
|
|
|
# Save the dir for the root of the Angular repo.
|
|
angular_dir=$(pwd)
|
|
|
|
# Switch into Material directory.
|
|
cd ${MATERIAL_REPO_TMP_DIR}
|
|
|
|
# Copy the test blocklist into the "angular/components" repository. The components
|
|
# repository automatically picks up the blocklist and disables the specified tests.
|
|
cp ${angular_dir}/tools/material-ci/test-blocklist.ts ${MATERIAL_REPO_TMP_DIR}/test/
|
|
|
|
# Create a symlink for the Bazel binary installed through NPM, as running through Yarn introduces OOM errors.
|
|
./scripts/circleci/setup_bazel_binary.sh
|
|
|
|
# Now actually run the tests. The dev-app and all its subpackages are excluded as they fail
|
|
# to compile due to limitations in Ivy's type checker (see FW-1352 and FW-1433)
|
|
bazel test --build_tag_filters=-docs-package,-e2e,-browser:firefox-local --test_tag_filters=-e2e,-browser:firefox-local --config=ivy -- src/... -src/dev-app/...
|