Closed
Bug 1479687
Opened 7 years ago
Closed 4 years ago
Assertion failed in time-zone-2038-pst.js building libjs 60
Categories
(Core :: JavaScript: Standard Library, defect, P5)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: heftig, Unassigned)
References
Details
I'm building libjs for Arch Linux. After upgrading from 52 to 60, we're seeing a regression running the jstests:
non262/Date/time-zone-2038-pst.js:43:5 Error: Assertion failed: got "Sat Mar 31 2040 00:00:00 GMT-0700 (PST)", expected "Sat Mar 31 2040 00:00:00 GMT-0700 (PDT)"
Code that builds libjs 60.1.0 (failing test excluded):
https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/js60&id=187998510daa061b197f33338d23a1d4e72e8acc
Code that builds libjs 52.9.0 (works):
https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/js52&id=e951ea66e876be8ee8594b1e142846b3ac27d9b4
I've also tested several official Firefox builds for their behavior by running (new Date(2040, 2, 31)).toString() in the console:
Firefox 60.1.0esr and 61.0.1 fail the test (output contains PST).
Firefox Nightly 62.0a1 and 63.0a1 pass the test (output contains PDT).
So I'm a bit confused. Is this test really supposed to be passed?
Comment 1•7 years ago
|
||
This sounds like the issue fixed in bug 1415202?
Reporter | ||
Comment 2•7 years ago
|
||
Applying the patch from bug 1415202 makes the test pass.
Comment 3•6 years ago
|
||
We don't typically backport fixes like this to the ultra-stable ESR branch.
Priority: -- → P5
Comment 4•4 years ago
|
||
ESR60 is no longer supported -> resolve as WONT FIX.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•