Source: mariadb
Version: 1:11.8.1-2
Followup-For: Bug #1084293
Control: tags -1 ftbfs
Hi!
I also hit this bug but I wonder why don't we set the test to a timezone
without daylight saving, like UTC...
...
main.timezone w7 [ retry-fail ]
Test ended at 2025-04-18 09:52:06
CURRENT_TEST: main.timezone
--- /build/reproducible-path/mariadb-11.8.1/mysql-test/main/timezone.result
2025-02-12 11:13:21.000000000 +0100
+++ /build/reproducible-path/mariadb-11.8.1/mysql-test/main/timezone.reject
2025-04-18 11:52:05.946929074 +0200
@@ -1,6 +1,6 @@
show variables like "system_time_zone";
Variable_name Value
-system_time_zone CET
+system_time_zone CEST
#
# Test unix timestamp
#
Result length mismatch
worker[07] mysql-test-run: WARNING: Test reserved for w32 picked up by w7
worker[07] > Restart - not started
- skipping
'/build/reproducible-path/mariadb-11.8.1/builddir/mysql-test/var/7/log/main.timezone/'
Test main.timezone has failed 2 times, no more retries!
...
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.21-amd64 (SMP w/128 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
