Michaël Zasso
Michaël Zasso
It means that the fast API is not called during the test. Have you not tried it locally with debug mode ?
/cc @nodejs/i18n-api This output change is weird: https://ci.nodejs.org/job/node-test-commit-linuxone/nodes=rhel9-s390x/52175/testReport/junit/(root)/parallel/test_datetime_change_notify/ ``` AssertionError [ERR_ASSERTION]: The input did not match the regular expression /Irish Standard Time|Greenwich Mean Time/. Input: '11/1/2025, 10:49:12 AM GMT+00:00' ```
/cc @srl295 The new output looks more like what we should get with [`timeZoneName: "longOffset"`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/DateTimeFormat/DateTimeFormat#longoffset)
I pushed an update to the test, but still not convinced that it's an expected change.
CLDR bug: https://unicode-org.atlassian.net/browse/CLDR-19136
https://unicode-org.atlassian.net/browse/ICU-23278 Let's wait for 78.2 or 79.1.
First improvement: https://github.com/image-js/image-js-typescript/pull/336
I doubt that your spectra strictly have integers between 0 and maxValue. How would you see them being converted?
Is there a world where using glibc 2.28 on RHEL 9 is an option?