Details
Major Description
Recent builds on the official Debian CI system started failing because the time zone in main.timezone changes. I don't know why it changed, and if it is a legit change or not. This upstream bug report is an ask to assess if the current hard-coded time zone value in the test makes sense or not.
main.timezone w4 [ fail ]
|
Test ended at 2024-10-06 06:28:50
|
CURRENT_TEST: main.timezone
|
--- /usr/share/mariadb/mariadb-test/main/timezone.result 2024-08-20 03:41:36.000000000 +0200
|
+++ /tmp/tmp.XgWRvorQ7g/var/4/log/timezone.reject 2024-10-06 08:28:49.819975055 +0200
|
@@ -1,6 +1,6 @@
|
show variables like "system_time_zone";
|
Variable_name Value
|
-system_time_zone MET
|
+system_time_zone CEST
|
#
|
# Test unix timestamp
|
#
|
@@ -82,7 +82,7 @@
|
SET @@time_zone= default;
|
SELECT DATE_FORMAT('2009-11-01 22:23:00', '%z %Z') AS current_timezone;
|
current_timezone
|
-+0100 MET
|
++0100 CET
|
SELECT DATE_FORMAT('2008-06-04 02:23:00', '%z %Z') AS current_timezone;
|
current_timezone
|
-+0200 MEST
|
++0200 CEST
|
Result length mismatch
|
See failures in action at e.g.
https://ci.debian.net/packages/m/mariadb/
-> https://ci.debian.net/packages/m/mariadb/unstable/amd64/52663812/#S14
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mariadb.html
-> https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/mariadb_11.4.3-1.rbuild.log.gz
https://salsa.debian.org/mariadb-team/mariadb-server/-/pipelines
-> https://salsa.debian.org/mariadb-team/mariadb-server/-/jobs/6245904