Changeset 269667 in webkit
- Timestamp:
- Nov 10, 2020 5:07:50 PM (3 years ago)
- Location:
- trunk/JSTests
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/JSTests/ChangeLog
r269590 r269667 1 2020-11-10 Michael Catanzaro <mcatanzaro@gnome.org> 2 3 stress/intl-datetimeformat-formatrange.js and stress/intl-datetimeformat-formatrange-relevant-extensions.js fail with ICU 65.1 4 https://bugs.webkit.org/show_bug.cgi?id=218763 5 6 Reviewed by Yusuke Suzuki. 7 8 Yesterday Red Hat upgraded its internal CI to Fedora 32 (ICU 65.1), causing 9 stress/intl-datetimeformat-formatrange-relevant-extensions.js and 10 stress/intl-datetimeformat-formatrange.js to begin failing. The problem is that the space 11 characters used in the range format changed at some point. The current version of the test 12 expects normal ASCII space characters for ICU 67 and newer, and special spaces for older 13 versions of ICU. 14 15 The test passes for me locally on Fedora 33 (ICU 67.1), so perhaps we just need to use the 16 new codepath for ICU 65 and 66 as well. 17 18 * stress/intl-datetimeformat-formatrange-relevant-extensions.js: 19 * stress/intl-datetimeformat-formatrange.js: 20 (test): 21 1 22 2020-11-09 Keith Miller <keith_miller@apple.com> 2 23 -
trunk/JSTests/stress/intl-datetimeformat-formatrange-relevant-extensions.js
r266033 r269667 20 20 21 21 function test() { 22 let range = " – "; // This is not usual space unfortuantely in ICU 66.23 if ($vm.icuVersion() > 66)22 let range = " – "; // This is not usual space unfortuantely in older ICU versions. 23 if ($vm.icuVersion() >= 65) 24 24 range = " – "; 25 25 -
trunk/JSTests/stress/intl-datetimeformat-formatrange.js
r266033 r269667 34 34 35 35 function test() { 36 let range = " – "; // This is not usual space unfortuantely in ICU 66.37 if ($vm.icuVersion() > 66)36 let range = " – "; // This is not usual space unfortuantely in older ICU versions. 37 if ($vm.icuVersion() >= 65) 38 38 range = " – "; 39 39
Note: See TracChangeset
for help on using the changeset viewer.