-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix the test test_get_tz_data_version in rust_icu_ucal #221
Comments
@kpozin FYI |
filmil
added a commit
to filmil/rust_icu
that referenced
this issue
Nov 11, 2021
Starting from ICU 70, the time zone data version can have more than a single letter after the release number. We used to have versions like `2020a`, `2020b` etc. With ICU 70, we get `2021a1`. We're adopting the same regex as in: https://fuchsia-review.googlesource.com/c/fuchsia/+/597898 for quick checks of the version string. Fixes: google#221
filmil
added a commit
to filmil/rust_icu
that referenced
this issue
Nov 11, 2021
Starting from ICU 70, the time zone data version can have more than a single letter after the release number. We used to have versions like `2020a`, `2020b` etc. With ICU 70, we get `2021a1`. We're adopting the same regex as in: https://fuchsia-review.googlesource.com/c/fuchsia/+/597898 for quick checks of the version string. Fixes: google#221
filmil
added a commit
that referenced
this issue
Nov 11, 2021
Starting from ICU 70, the time zone data version can have more than a single letter after the release number. We used to have versions like `2020a`, `2020b` etc. With ICU 70, we get `2021a1`. We're adopting the same regex as in: https://fuchsia-review.googlesource.com/c/fuchsia/+/597898 for quick checks of the version string. Fixes: #221
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I get the following:
The regex used for tz data version matching trips up at the extra
1
at the end of2021a1
.The text was updated successfully, but these errors were encountered: