This repository was archived by the owner on Apr 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 27.4k
Chrome unit test fails on newly clean build (mock.tzDate) (Expected '12/31/1969' to match '1970') #14272
Milestone
Comments
Reference to the same problem. |
Unit tests fail when run in Australia #5017 |
Local fail on master on one of date filter tests #4218 |
date filter not adding appropriate + / - sign for 'Z' timezone offset resulting in invalid ISO 8601 #1532 Perhaps related ... |
fix it :D |
gkalpak
added a commit
to gkalpak/angular.js
that referenced
this issue
Mar 21, 2016
Probably due to implementation differences in browsers for pre-DST period (see angular#5017 and especially angular#5017 (comment) for context), some `TzDate` tests had different behavior on different Timezones/Regions (e.g. failed in Australia, which started to observe DST in 1971). Since the used year (`1970`) didn't have any particular significance, this commit fixes the issue by using a year that is more consistently handled by browsers (`2000`). Fixes angular#14272
Sure I will give it a try later today. |
@gkalpak #14285 indeed Fixed the issue. I changed the getLocalDateString test as in:
So i guess this will work over all the browsers that maintain differences over their pre-DST time implementation. Thanks gkalpak, greetings. The results:
|
gkalpak
added a commit
that referenced
this issue
Mar 21, 2016
Probably due to implementation differences in browsers for pre-DST period (see #5017 and especially #5017 (comment) for context), some `TzDate` tests had different behavior on different Timezones/Regions (e.g. failed in Australia, which started to observe DST in 1971). Since the used year (`1970`) didn't have any particular significance, this commit fixes the issue by using a year that is more consistently handled by browsers (`2000`). Fixes #14272 Closes #14285
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Unit Test suite fails on Chrome at test # 5146
What is the expected behavior?
All test should pass on a clean build.
I've just cloned the '/angular/angular.js' (Version 1.5.1), build it without errors and with the clean build when run the preloaded unit tests with grunt (grunt test:unit) it throws the same error mentioned by @wagnerfrancisco when tests Chrome.
(All the test PASS except this one)
Reproducable: Always
Browser: Chrome 49.0.2623
Operating System: Ubuntu 15.10 (Wily Werewolf)
steps to reproduce:
1)Clone the repository of Angular.js
2)Building & Testing
Have node v 0.12.4 pre-installed
Have java version 1.8.0_74 pre-installed
Install Grunt & Bower:
3)Running the Test Suite
The piece of code that runs this test is:
(/angular.js/test/ngMock/angular-mocksSpec.js)
and the code that is referenced:
(/angular.js/src/ngMock/angular-mock.js)
I want to contribute to the angular.js project but I'm not sure if this is a legit problem to work on
sorry if the post is too long :).
The text was updated successfully, but these errors were encountered: