1928015 - js/src/tests/non262/Date/parse-dashed-numeric-date.js relies on legacy MST time zone

Status: RESOLVED FIXED

(Core :: JavaScript: Standard Library, defect, P3)

Description

[Simon McVittie]

Steps to reproduce:

Build Spidermonkey 128.4.0 (or 128.3.0) on a Debian unstable (development/rolling release) system, with tzdata 2024b-3, and without installing tzdata-legacy

Actual results:

non262/Date/parse-dashed-numeric-date.js: rc = 3, run time = 0.011593

/<<PKGBUILDDIR>>/js/src/tests/non262/Date/parse-dashed-numeric-date.js:119:13 Error: Assertion failed: got 568962338400000, expected 568962313200000: "19999-09-12 22:00:00 GMT-0800" should be Sun Sep 12 19999 23:00:00 GMT+0000 (GMT) (got Mon Sep 13 19999 06:00:00 GMT+0000 (GMT)).
Stack:
@/<<PKGBUILDDIR>>/js/src/tests/non262/Date/parse-dashed-numeric-date.js:119:13
inTimeZone@/<<PKGBUILDDIR>>/js/src/tests/non262/Date/shell.js:95:13
@/<<PKGBUILDDIR>>/js/src/tests/non262/Date/parse-dashed-numeric-date.js:7:11
TEST-UNEXPECTED-FAIL | non262/Date/parse-dashed-numeric-date.js | (args: "") [0.0 s]

Expected results:

tests pass

Comment 1

[Simon McVittie]

Attachment: js/src/tests: Avoid using legacy MST time zone name

The MST time zone name only exists in tzdata for compatibility with
Unix System V, and was moved to a legacy section in tzdata commit
a0b09c0 "Mark CET, CST6CDT etc. as obsolescent". On recent
Debian and Ubuntu systems, the time zones affected by this change
are only available if the additional tzdata-legacy package is installed.

Comment 2

[André Bargull [:anba]]

Fixed as part of the ICU update in bug 2000225.