Bug 210604 - REGRESSION(r260145/r260146): Two new failing i18n tests
Summary: REGRESSION(r260145/r260146): Two new failing i18n tests
Status: RESOLVED DUPLICATE of bug 210605
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: WebKit Nightly Build
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-16 06:54 PDT by Michael Catanzaro
Modified: 2020-04-16 11:25 PDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Catanzaro 2020-04-16 06:54:41 PDT 
Running stress/date-toLocaleString.js.default
stress/date-toLocaleString.js.default: Exception: Error: expected 1969(ji-you), 4:00:00 PM but got 1969(ji-you), 12:00:00 AM
stress/date-toLocaleString.js.default: shouldBe@date-toLocaleString.js:3:24
stress/date-toLocaleString.js.default: global code@date-toLocaleString.js:129:9
stress/date-toLocaleString.js.default: ERROR: Unexpected exit code: 3
FAIL: stress/date-toLocaleString.js.default

Running stress/date-toLocaleString.js.mini-mode
stress/date-toLocaleString.js.mini-mode: Exception: Error: expected 1969(ji-you), 4:00:00 PM but got 1969(ji-you), 12:00:00 AM
stress/date-toLocaleString.js.mini-mode: shouldBe@date-toLocaleString.js:3:24
stress/date-toLocaleString.js.mini-mode: global code@date-toLocaleString.js:129:9
stress/date-toLocaleString.js.mini-mode: ERROR: Unexpected exit code: 3
FAIL: stress/date-toLocaleString.js.mini-mode

The two above tests seem to have grown a dependency on system timezone. We used to have a bunch of tests with this problem and tbh I don't remember how we handled it in the past.
Comment 1 Ross Kirsling 2020-04-16 10:59:18 PDT 
Whoops, the other tests in that file specify `timeZone: 'UTC'`. Will fix.
Comment 2 Ross Kirsling 2020-04-16 11:25:13 PDT 
This technically isn't a duplicate, but I'm gonna handle these failures in one batch, so I'll have you verify the fix in one place. :)

*** This bug has been marked as a duplicate of bug 210605 ***