[Webkit-unassigned] [Bug 210605] New: REGRESSION(r259480): Two new failing i18n tests

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Apr 16 07:00:11 PDT 2020


https://bugs.webkit.org/show_bug.cgi?id=210605

            Bug ID: 210605
           Summary: REGRESSION(r259480): Two new failing i18n tests
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: mcatanzaro at gnome.org
                CC: clopez at igalia.com, ross.kirsling at sony.com,
                    tpopela at redhat.com

Running stress/intl-datetimeformat.js.default
stress/intl-datetimeformat.js.default: Exception: Error: expected Etc/UTC but got UTC
stress/intl-datetimeformat.js.default: shouldBe at intl-datetimeformat.js:3:24
stress/intl-datetimeformat.js.default: global code at intl-datetimeformat.js:245:9
stress/intl-datetimeformat.js.default: ERROR: Unexpected exit code: 3
FAIL: stress/intl-datetimeformat.js.default

Running stress/intl-datetimeformat.js.mini-mode
stress/intl-datetimeformat.js.mini-mode: Exception: Error: expected Etc/UTC but got UTC
stress/intl-datetimeformat.js.mini-mode: shouldBe at intl-datetimeformat.js:3:24
stress/intl-datetimeformat.js.mini-mode: global code at intl-datetimeformat.js:245:9
stress/intl-datetimeformat.js.mini-mode: ERROR: Unexpected exit code: 3
FAIL: stress/intl-datetimeformat.js.mini-mode

And these two tests expect UTC to be named differently. These tests starting failing in our internal nightly CI on April 3 (sorry for delay), so it's surely due to r259480 "Move Intl tests from LayoutTests to JSTests." The failing check is:

// Default time zone is a valid canonical time zone.
shouldBe(Intl.DateTimeFormat('en', { timeZone: Intl.DateTimeFormat().resolvedOptions().timeZone }).resolvedOptions().timeZone, Intl.DateTimeFormat().resolvedOptions().timeZone);

TBH I'm not sure what to do about this one. Is it a code bug, or a test bug...? Surely we can work around the error by changing the timezone on the system, but nicer to not do that.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20200416/0c507bd7/attachment.htm>


More information about the webkit-unassigned mailing list