Add expected failures for CLDR >= 46 #315
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ICU 76.1 / CLDR 46 got backported to Node 20.19 LTS, which is now in the GitHub CI. We need a CLDR 46 expected failures file until we can update to a version of test262 where this failure has been fixed.
ptomato
force-pushed
the
expected-failures-cldr46
branch
from
1bded43 to
e8d0c99
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ICU 76.1 / CLDR 46 got backported to Node 20.19 LTS, which is now in the GitHub CI. We need a CLDR 46 expected failures file until we can update to a version of test262 where this failure has been fixed.