2017-01-27 12:17:50 -05:00
|
|
|
#!/usr/bin/env bash
|
|
|
|
|
2018-04-23 14:46:02 -04:00
|
|
|
set -u -e -o pipefail
|
2017-01-27 12:17:50 -05:00
|
|
|
|
2018-03-15 18:36:11 -04:00
|
|
|
# see https://circleci.com/docs/2.0/env-vars/#circleci-built-in-environment-variables
|
|
|
|
CI=${CI:-false}
|
2018-02-27 17:06:06 -05:00
|
|
|
|
2018-03-15 18:36:11 -04:00
|
|
|
cd "$(dirname "$0")"
|
2017-01-27 12:17:50 -05:00
|
|
|
|
2018-03-15 18:36:11 -04:00
|
|
|
# basedir is the workspace root
|
|
|
|
readonly basedir=$(pwd)/..
|
2019-10-05 23:06:53 -04:00
|
|
|
readonly bazel_bin=$(yarn bin)/bazel
|
2017-11-18 15:26:33 -05:00
|
|
|
|
2019-01-06 06:37:46 -05:00
|
|
|
# When running on the CI, we track the payload size of various integration output files. Also
|
|
|
|
# we shard tests across multiple CI job instances. The script needs to be run with a shard index
|
|
|
|
# and the maximum amount of shards available for the integration tests on the CI.
|
|
|
|
# For example: "./run_tests.sh {SHARD_INDEX} {MAX_SHARDS}".
|
2018-03-15 18:36:11 -04:00
|
|
|
if $CI; then
|
|
|
|
source ${basedir}/scripts/ci/payload-size.sh
|
2018-04-23 14:46:02 -04:00
|
|
|
|
2019-01-06 06:37:46 -05:00
|
|
|
SHARD_INDEX=${1:?"No shard index has been specified."}
|
|
|
|
MAX_SHARDS=${2:?"The maximum amount of shards has not been specified."}
|
|
|
|
|
|
|
|
# Determines the tests that need to be run for this shard index.
|
|
|
|
TEST_DIRS=$(node ./get-sharded-tests.js --shardIndex ${SHARD_INDEX} --maxShards ${MAX_SHARDS})
|
|
|
|
|
2019-11-14 19:56:55 -05:00
|
|
|
# NB: we don't run build-packages-dist.js because we expect that it was done
|
2018-04-23 14:46:02 -04:00
|
|
|
# by an earlier job in the CircleCI workflow.
|
|
|
|
else
|
|
|
|
# Not on CircleCI so let's build the packages-dist directory.
|
|
|
|
# This should be fast on incremental re-build.
|
2019-11-14 19:56:55 -05:00
|
|
|
node ${basedir}/scripts/build-packages-dist.js
|
2019-01-06 06:37:46 -05:00
|
|
|
|
|
|
|
# If we aren't running on CircleCI, we do not shard tests because this would be the job of
|
|
|
|
# Bazel eventually. For now, we just run all tests sequentially when running locally.
|
|
|
|
TEST_DIRS=$(ls | grep -v node_modules)
|
2018-03-20 15:34:27 -04:00
|
|
|
fi
|
2017-08-03 18:18:55 -04:00
|
|
|
|
2017-02-10 19:23:44 -05:00
|
|
|
# Workaround https://github.com/yarnpkg/yarn/issues/2165
|
|
|
|
# Yarn will cache file://dist URIs and not update Angular code
|
fix(ngcc): do not collect private declarations from external packages (#34811)
Previously, while trying to build an `NgccReflectionHost`'s
`privateDtsDeclarationMap`, `computePrivateDtsDeclarationMap()` would
try to collect exported declarations from all source files of the
program (i.e. without checking whether they were within the target
package, as happens for declarations in `.d.ts` files).
Most of the time, that would not be a problem, because external packages
would be represented as `.d.ts` files in the program. But when an
external package had no typings, the JS files would be used instead. As
a result, the `ReflectionHost` would try to (unnecessarilly) parse the
file in order to extract exported declarations, which in turn would be
harmless in most cases.
There are certain cases, though, where the `ReflectionHost` would throw
an error, because it cannot parse the external package's JS file. This
could happen, for example, in `UmdReflectionHost`, which expects the
file to contain exactly one statement. See #34544 for more details on a
real-world failure.
This commit fixes the issue by ensuring that
`computePrivateDtsDeclarationMap()` will only collect exported
declarations from files within the target package.
Jira issue: [FW-1794](https://angular-team.atlassian.net/browse/FW-1794)
Fixes #34544
PR Close #34811
2020-01-15 14:54:36 -05:00
|
|
|
export readonly cache=.yarn_local_cache
|
2017-02-10 19:23:44 -05:00
|
|
|
function rm_cache {
|
|
|
|
rm -rf $cache
|
|
|
|
}
|
|
|
|
rm_cache
|
|
|
|
mkdir $cache
|
|
|
|
trap rm_cache EXIT
|
|
|
|
|
2019-01-06 06:37:46 -05:00
|
|
|
for testDir in ${TEST_DIRS}; do
|
2017-01-27 12:17:50 -05:00
|
|
|
[[ -d "$testDir" ]] || continue
|
|
|
|
echo "#################################"
|
|
|
|
echo "Running integration test $testDir"
|
|
|
|
echo "#################################"
|
|
|
|
(
|
|
|
|
cd $testDir
|
2017-08-03 18:18:55 -04:00
|
|
|
rm -rf dist
|
2018-04-23 14:46:02 -04:00
|
|
|
|
2019-11-25 10:48:18 -05:00
|
|
|
# Ensure the versions of (non-local) dependencies are exact versions (not version ranges) and
|
|
|
|
# in-sync between `package.json` and the lockfile.
|
|
|
|
# (NOTE: This must be run before `yarn install`, which updates the lockfile.)
|
|
|
|
node ../check-dependencies .
|
|
|
|
|
2017-02-10 19:23:44 -05:00
|
|
|
yarn install --cache-folder ../$cache
|
2017-02-09 12:08:16 -05:00
|
|
|
yarn test || exit 1
|
2018-10-31 07:03:22 -04:00
|
|
|
|
2019-10-02 07:28:23 -04:00
|
|
|
# Track payload size for cli-hello-world* tests, plus hello_world__closure
|
|
|
|
if $CI && ([[ $testDir =~ cli-hello-world ]] || [[ $testDir == hello_world__closure ]]); then
|
|
|
|
if ([[ $testDir =~ cli-hello-world ]]); then
|
2017-08-03 18:18:55 -04:00
|
|
|
yarn build
|
|
|
|
fi
|
2018-10-31 07:03:22 -04:00
|
|
|
|
2019-11-22 08:16:39 -05:00
|
|
|
trackPayloadSize "$testDir" "dist/*.js" true "${basedir}/integration/_payload-limits.json"
|
2018-01-25 19:43:29 -05:00
|
|
|
fi
|
2018-10-31 07:03:22 -04:00
|
|
|
|
2018-03-15 18:36:11 -04:00
|
|
|
# remove the temporary node modules directory to keep the source folder clean.
|
|
|
|
rm -rf node_modules
|
2017-01-27 12:17:50 -05:00
|
|
|
)
|
|
|
|
done
|
2017-08-03 18:18:55 -04:00
|
|
|
|
2019-11-22 10:02:09 -05:00
|
|
|
if $CI && [[ "$SHARD_INDEX" == "0" ]]; then
|
2019-11-22 08:16:39 -05:00
|
|
|
trackPayloadSize "umd" "../dist/packages-dist/*/bundles/*.umd.min.js" false
|
2018-10-31 07:03:22 -04:00
|
|
|
fi
|