jiff/scripts
Andrew Gallant 08abeadd09 tz: fallback to Etc/Unknown when TZ is set to an invalid value
Previously, when `TZ` was set to an invalid value, Jiff would still
attempt to detect the system configured time zone. But this is arguably
not great, because it silently (aside from logs) rejects an invalid
`TZ` value. In reality, if `TZ` is set, it is likely that the user
intends for it to have an impact. So if it doesn't, we should bleat
about it.

This manifests as an error when using `TimeZone::try_system()` and
manifests as a error sentinel in the form of `Etc/Unknown` when using
`TimeZone::system()`.

We also tweak some of the logging levels. Namely, in #370, I increased
the number of TRACE-level log messages, which makes it much noisier. So
I've promoted a few things that were TRACE to DEBUG without making the
output much noisier. I guess TRACE should be reserved for variable
length things.

Fixes #364
2025-05-17 11:02:57 -04:00
..
jiff-debug tz: add support for the Android platform 2025-01-12 15:38:41 -05:00
test ci: break ./scripts/test into pieces... 2025-03-06 16:05:00 -05:00
test-all ci: break ./scripts/test into pieces... 2025-03-06 16:05:00 -05:00
test-default ci: break ./scripts/test into pieces... 2025-03-06 16:05:00 -05:00
test-examples cargo: restore sanity to iterative development 2025-04-10 20:54:30 -04:00
test-integrations jiff-icu: compatibility fixes 2025-05-01 15:56:34 -04:00
test-only-bundle ci: break ./scripts/test into pieces... 2025-03-06 16:05:00 -05:00
test-only-core ci: break ./scripts/test into pieces... 2025-03-06 16:05:00 -05:00
test-programs tz: fallback to Etc/Unknown when TZ is set to an invalid value 2025-05-17 11:02:57 -04:00
test-various-feature-combos cargo: fix compilation when only tzdb-concatenated is enabled 2025-05-07 19:03:26 -04:00
test-wasm scripts: fix test-wasm 2025-03-06 16:05:00 -05:00