I am able to reproduce the FTBFS in a schroot, sans tzdata package.

However, this is weird, because Go ships with an embedded copy of tzdata (https://pkg.go.dev/time/tzdata). AFAICT, this is not stripped out in Debian golang-go packages.

Only selected tests fails, and only those which reference certain timezones:

--- FAIL: TestFmtTimeFull (0.00s)
    en_test.go:673: Expected '<nil>' Got 'unknown time zone America/Toronto'

--- FAIL: TestFmtTimeFull (0.00s)
    ja_test.go:641: Expected '<nil>' Got 'unknown time zone Asia/Tokyo'

--- FAIL: TestFmtTimeFull (0.00s)
    ja_JP_test.go:641: Expected '<nil>' Got 'unknown time zone Asia/Tokyo'

--- FAIL: TestFmtTimeFull (0.00s)
    ru_RU_test.go:834: Expected '<nil>' Got 'unknown time zone America/Toronto'

I don't quite understand what America/Toronto has got to do with the ru_RU locale, however that zone appears in virtually all other "unrelated" tests (albeit commented out). It looks like an oversight that it was uncommented in the ru_RU_test.go.

In fact, the _only_ two timezones referred to in this package are "America/Toronto" (always commented out except in en_test and ru_RU_test.go), and "Asia/Tokyo" - so perhaps it's not just something that affects certain timezones, but rather the mere fact that the package only refers to a tiny subset of the available timezones.

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to