@petebacondarwin Would you please just let me know why are circle ci tests failing?

@basherr - it looks like the CI is being run under your account rather than Angular's. Did you turn on CircleCI integration for your own fork? I suggest turning that off since it might be blocking the normal Angular CI running?

@basherr - it looks like the CI is being run under your account rather than Angular's. Did you turn on CircleCI integration for your own fork? I suggest turning that off since it might be blocking the normal Angular CI running?

Is there a way to re-run the tests? Just turned off CircleCi on my fork. Thanks

@basherr - it looks like the CI is being run under your account rather than Angular's. Did you turn on CircleCI integration for your own fork? I suggest turning that off since it might be blocking the normal Angular CI running?

Is there a way to re-run the tests? Just turned off CircleCi on my fork. Thanks

The CI run is failing because the commits need to be rebased on top of latest master. The instructions are provided in the CI job:

        CircleCI config on master has been modified since commit 6d13473,
        which this PR is based on.

        Please rebase the PR on master after fetching from upstream.

        Rebase instructions for PR Author, please run the following commands:

          git fetch upstream master;
          git checkout fix-animation-driver-query;
          git rebase upstream/master;
          git push --force-with-lease;

In this case, you'll also want to squash all commits into a single one, so you'll want to run an interactive rebase and mark all commits but the first as squash.

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

Hi @basherr,

Could you please squash all commits in this PR and update commit message (git commit --amend)?

Here is my proposal (based on the comments in the code):

fix(animations): replace copy of query selector node-list from "spread" to "for"

For element queries that return sufficiently large NodeList objects, using spread syntax
to populate the results array causes a RangeError due to the call stack limit being reached.
This commit updates the code to use regular "for" loop instead.

Fixes #38551.

Thank you.

@AndrewKushnir The build fails due to the commit message body being too long. What about the following only?

fix(animations): replace copy of query selector node-list from "spread" to "for"

The spread syntax fails to copy a sufficiently large number of Nodelist due to callstack limit being reached. 

@basherr - it is only the length of "each line" that must be under 120 chars I suspect that you put the whole body in a single line? Try splitting the body into multiple lines like in @AndrewKushnir's example.

Also there are still 2 commits in this PR. Can you squash them into one?

@AndrewKushnir @petebacondarwin All set! thanks for your help. However, the reviewers seem too much occupied.

presubmit

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}