[#111472] [Ruby master Bug#19274] Error installing ruby 3.2.0 on RH 8 — "aalllop (Alberto Allegue) via ruby-core" <ruby-core@...>
Issue #19274 has been reported by aalllop (Alberto Allegue).
5 messages
2022/12/28
[#111508] Data support for versions before 3.2.0 — Eustáquio Rangel via ruby-core <ruby-core@...>
I was wondering that every piece of code (gems, etc) that use the new Data =
3 messages
2022/12/29
[ruby-core:111379] [Ruby master Bug#19187] Ruby 3.1.3 testsuite fails after timezone 2022g update is applied
From:
duerst via ruby-core <ruby-core@...>
Date:
2022-12-22 06:00:37 UTC
List:
ruby-core #111379
Issue #19187 has been updated by duerst (Martin D=FCrst). mame (Yusuke Endoh) wrote in #note-7: > I disagree with simply erasing the tests depending on tzdata. > Following changes in tzdata is a bit annoying, but I don't think it's hap= pening so frequently. I agree. In particular, this test was for 1981. Data about 1981 should only= change very infrequently, essentially only when a mistake in tzdata is det= ected and fixed. ---------------------------------------- Bug #19187: Ruby 3.1.3 testsuite fails after timezone 2022g update is appli= ed https://bugs.ruby-lang.org/issues/19187#change-100754 * Author: coolo (Stephan Kulow) * Status: Closed * Priority: Normal * ruby -v: ruby 3.1.3p185 (2022-11-24 revision 1a6b16756e) [x86_64-linux-gn= u] * Backport: 2.7: DONE, 3.0: DONE, 3.1: DONE ---------------------------------------- The timezone database changed incompatible to what ruby's testsuite expects. See the announcement here: http://mm.icann.org/pipermail/tz-announce/2022-N= ovember/000076.html and note the little detail Singapore's 1981-12-31 change was at 16:00 UTC (23:30 local time), not 24:00 local time. (Thanks to Geoff Clare via Robert Elz.) Problem is that test/ruby/test_time_tz.rb tests this very detail in 3 place= s - and breaks. 1) Failure: TestTimeTZ#test_asia_singapore [/home/abuild/rpmbuild/BUILD/ruby-3.1.3/test= /ruby/test_time_tz.rb:143]: TZ=3DAsia/Singapore Time.local(1981, 12, 31, 23, 59, 59). <"1981-12-31 23:59:59 +0730"> expected but was <"1982-01-01 00:29:59 +0800">. 2) Failure: TestTimeTZ#test_gen_Asia_Singapore_22 [/home/abuild/rpmbuild/BUILD/ruby-3.1= .3/test/ruby/test_time_tz.rb:382]: TZ=3DAsia/Singapore Time.utc(1981, 12, 31, 16, 29, 59).localtime. <"1981-12-31 23:59:59 +0730"> expected but was <"1982-01-01 00:29:59 +0800">. 3) Failure: TestTimeTZ#test_gen_Asia_Singapore_45 [/home/abuild/rpmbuild/BUILD/ruby-3.1= .3/test/ruby/test_time_tz.rb:400]: TZ=3DAsia/Singapore Time.local(1981, 12, 31, 23, 59, 59). <"1981-12-31 23:59:59 +0730"> expected but was <"1982-01-01 00:29:59 +0800">. I can see no other option than not to test this detail - because relying on= correct timezone data (either way) is barely possible. --=20 https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- [email protected] To unsubscribe send an email to [email protected] ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-c= ore.ml.ruby-lang.org/