-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Conversation
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@crisbeto Thank you. |
@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? |
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. |
Nice 😄 I was wondering why I get out-of-memory issues on Chrome. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
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 withinstanceof
checks which accomplish the same.Fixes #4654.