Bug 3762 - REGRESSION fast/js/date-parse-test fails
Summary: REGRESSION fast/js/date-parse-test fails
Status: VERIFIED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 412
Hardware: Mac OS X 10.4
: P1 Normal
Assignee: Maciej Stachowiak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-29 01:40 PDT by mitz
Modified: 2005-07-03 14:28 PDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mitz 2005-06-29 01:40:01 PDT
fast/js/date-parse-test fails with TOT:

called Date.parse on Dec 25 1995 GMT and got NaN instead of 819849600000

called Date.parse on Dec 25 1995 1:30AM and got NaN instead of 819847800000

called Date.parse on Dec 25 1995 1:30PM and got NaN instead of 819891000000

called Date.parse on Dec 25 1995 UTC and got NaN instead of 819849600000

called Date.parse on Dec 25 1995 UT and got NaN instead of 819849600000

called Date.parse on Dec 25 1995 PST and got NaN instead of 819878400000

called Date.parse on Dec 25 1995 PDT and got NaN instead of 819874800000

called Date.parse on Dec 25 1995 XXX and got NaN instead of 819849600000

called Date.parse on Dec 25 1995 1:30 XXX and got 819847800000 instead of 819855000000

called Date.parse on Dec 25 1995 1:30 U and got 819847800000 instead of 819855000000

called Date.parse on Dec 25 1995 1:30 V and got 819847800000 instead of 819855000000

called Date.parse on Dec 25 1995 1:30 W and got 819847800000 instead of 819855000000

called Date.parse on Dec 25 1995 1:30 X and got 819847800000 instead of 819855000000

called Date.parse on Dec 25 1995 0:30 AM GMT and got 819851400000 instead of NaN

called Date.parse on Dec 25 1995 0:30 PM GMT and got 819894600000 instead of NaN

Testing complete. 15 tests failed.
Comment 1 Maciej Stachowiak 2005-06-29 01:46:25 PDT
Likely a regression due to the fix for http://bugzilla.opendarwin.org/show_bug.cgi?id=3477
 
Comment 2 Joost de Valk (AlthA) 2005-06-29 01:47:07 PDT
Confirmed. 
Comment 3 Carsten Guenther 2005-06-30 17:57:10 PDT
This one has been fixed by rolling out the patch for bug 3477.