From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-3.0 required=3.0 tests=AWL,BAYES_00,DKIM_INVALID, DKIM_SIGNED,MAILING_LIST_MULTI,RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DNSWL_HI, SPF_HELO_PASS,SPF_PASS,UNPARSEABLE_RELAY shortcircuit=no autolearn=no autolearn_force=no version=3.4.2 Received: from nue.mailmanlists.eu (nue.mailmanlists.eu [IPv6:2a01:4f8:1c0c:6b10::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id AC9F21F601 for ; Wed, 7 Dec 2022 10:41:43 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=ruby-lang.org header.i=@ruby-lang.org header.b="jwMmkhc6"; dkim-atps=neutral Received: from nue.mailmanlists.eu (localhost [127.0.0.1]) by nue.mailmanlists.eu (Postfix) with ESMTP id D44F57E5FE; Wed, 7 Dec 2022 10:41:34 +0000 (UTC) Authentication-Results: nue.mailmanlists.eu; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=ruby-lang.org header.i=@ruby-lang.org header.a=rsa-sha256 header.s=s1 header.b=jwMmkhc6; dkim-atps=neutral Received: from xtrwkhkc.outbound-mail.sendgrid.net (xtrwkhkc.outbound-mail.sendgrid.net [167.89.16.28]) by nue.mailmanlists.eu (Postfix) with ESMTPS id CDA3D7E5E5 for ; Wed, 7 Dec 2022 10:41:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ruby-lang.org; h=from:references:subject:mime-version:content-type: content-transfer-encoding:list-id:to:cc:content-type:from:subject:to; s=s1; bh=Q7ge9rKJvMRLmoa7z7K4capMvZqdAbll18cepDzVOsg=; b=jwMmkhc6c4V3yjM5PEvZ9iXURcwFQ/UGRS+i/FzQrblQGrioMKx44i2fTRpu2AtVS+RT 1sQWYVE2eIsKOA1drebu4n+4wqHdoz6CoGQXxDmIuSt2kQtBV6yi6KhBA/laj0LZq/zR8Z ixswwPy/Q7jI8Lj332qOUNKY0rK6fgE4v0jfvIpqiIFrgzuHtxjWfZiQ/cNWAOQl3KIjLo w2HC9krkE6tC1zma8+j2Ivu7EUZuJUYxF2egDVaKcfgFMOs3uSQ6V8eppdaTDJHcfnfK5g WtzfpZdKDUCCU3EeEWTisEockMUt3aO4HU2rBq+POKbf11jVmQeZ13VpaE19s+Jw== Received: by filterdrecv-canary-666d4cffc-t7sp2 with SMTP id filterdrecv-canary-666d4cffc-t7sp2-1-63906DD9-39 2022-12-07 10:41:29.667158408 +0000 UTC m=+1683283.289297433 Received: from herokuapp.com (unknown) by geopod-ismtpd-3-3 (SG) with ESMTP id GYoDzUqtRHy0gylFVGJzdA for ; Wed, 07 Dec 2022 10:41:29.594 +0000 (UTC) Date: Wed, 07 Dec 2022 10:41:29 +0000 (UTC) From: "nagachika (Tomoyuki Chikanaga)" Message-ID: References: Mime-Version: 1.0 X-Redmine-Project: ruby-master X-Redmine-Issue-Tracker: Bug X-Redmine-Issue-Id: 19187 X-Redmine-Issue-Author: coolo X-Redmine-Sender: nagachika X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-Redmine-MailingListIntegration-Message-Ids: 87585 X-SG-EID: =?us-ascii?Q?5tswmMdpuZtWC+SIdASU151b2aqPGWt2MCGiK8FM5waeDDbfOiDH=2FZvzDCybLH?= =?us-ascii?Q?ac5aUpPkJl2qsSCwuuhJa5kBFsc=2FNuo8RbFzwG3?= =?us-ascii?Q?LHWVN=2Fhv6EjFGdg61fY31lDM8EoL5sV=2FXiuOzXo?= =?us-ascii?Q?DQjN0qT0HJy6mgZbzGXLH=2FfYugzQz1UKvAZQ5Cy?= =?us-ascii?Q?YL0ZR5yQ1hK5To05io=2FWtbbkR=2F4o2EDYQHp3je5?= =?us-ascii?Q?Hwbe5SHLAmcyIWS6mROPMGTkoqG3gTnFmWTDVwk?= =?us-ascii?Q?VfSW0NzzebusIVC5Sj0hMBFHy88kPAyEhoNssDm?= =?us-ascii?Q?zNA=3D?= To: ruby-core@ml.ruby-lang.org X-Entity-ID: b/2+PoftWZ6GuOu3b0IycA== Message-ID-Hash: ZBVJPSOLVJWCQCQZSMKBREPG2NDZ7AO5 X-Message-ID-Hash: ZBVJPSOLVJWCQCQZSMKBREPG2NDZ7AO5 X-MailFrom: bounces+313651-b711-ruby-core=ml.ruby-lang.org@em5188.ruby-lang.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.3 Precedence: list Reply-To: Ruby developers Subject: [ruby-core:111230] [Ruby master Bug#19187] Ruby 3.1.3 testsuite fails after timezone 2022g update is applied List-Id: Ruby developers Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Issue #19187 has been updated by nagachika (Tomoyuki Chikanaga). Status changed from Open to Closed Backport changed from 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN to 2.7: REQUIRED, 3.0: REQUIRED, 3.1: REQUIRED The workaround was committed to master branch at 58cc3c9f387dcf8f820b43e043b540fa06248da3. ---------------------------------------- Bug #19187: Ruby 3.1.3 testsuite fails after timezone 2022g update is applied https://bugs.ruby-lang.org/issues/19187#change-100518 * Author: coolo (Stephan Kulow) * Status: Closed * Priority: Normal * ruby -v: ruby 3.1.3p185 (2022-11-24 revision 1a6b16756e) [x86_64-linux-gnu] * Backport: 2.7: REQUIRED, 3.0: REQUIRED, 3.1: REQUIRED ---------------------------------------- The timezone database changed incompatible to what ruby's testsuite expects. See the announcement here: http://mm.icann.org/pipermail/tz-announce/2022-November/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 places - and breaks. 1) Failure: TestTimeTZ#test_asia_singapore [/home/abuild/rpmbuild/BUILD/ruby-3.1.3/test/ruby/test_time_tz.rb:143]: TZ=Asia/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=Asia/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=Asia/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. -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/