Skip to content

test: fix infinite loop in tests #4662

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 22, 2017

Conversation

crisbeto
Copy link
Member

Fixes some unit tests going into an infinite loop by using the jasmine.any matcher. Not exactly sure what is going on, but it was most likely introduced in Jasmine 2.6.2. For now I've replaced those matches with instanceof checks which accomplish the same.

Fixes #4654.

Fixes some unit tests going into an infinite loop by using the `jasmine.any` matcher. Not exactly sure what is going on, but it was most likely introduced in Jasmine 2.6.2. For now I've replaced those matches with `instanceof` checks which accomplish the same.

Fixes angular#4654.
@crisbeto crisbeto changed the title test: infinite loop in tests test: fix infinite loop in tests May 18, 2017
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels May 18, 2017
@RobJacobs
Copy link
Contributor

@crisbeto Thank you.

@RobJacobs
Copy link
Contributor

@crisbeto Curious as to why the Travis CI build didn't fail? Looking at the Travis logs on some of the recent commits it doesn't list a job with MODE=test like you see with MODE=e2e?

@crisbeto
Copy link
Member Author

crisbeto commented May 19, 2017

My guess is that it had a slightly older version of Jasmine in the cache, which wasn't problematic. At the time I submitted the PR, Jasmine 2.6.2 had been released for about 20 hours.

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label May 19, 2017
@devversion
Copy link
Member

Nice 😄 I was wondering why I get out-of-memory issues on Chrome.

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Gulp test tasks are failing
5 participants