Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
11.8
-
None
Description
Similar to MDEV-9270 but now for architecture x32, when running --big-test I saw these failures:
mroonga/storage.column_datetime_32bit_2038 w1 [ fail ]
|
Test ended at 2025-12-12 09:31:40
|
|
|
CURRENT_TEST: mroonga/storage.column_datetime_32bit_2038
|
--- /build/reproducible-path/mariadb-11.8.5/storage/mroonga/mysql-test/mroonga/storage/r/column_datetime_32bit_2038.result 2025-11-13 08:45:32.000000000 +0000
|
+++ /build/reproducible-path/mariadb-11.8.5/storage/mroonga/mysql-test/mroonga/storage/r/column_datetime_32bit_2038.reject 2025-12-12 09:31:39.674093484 +0000
|
@@ -8,10 +8,8 @@
|
VALUES ('2038-01-18 03:14:07', '2038-01-18 03:14:07');
|
INSERT IGNORE INTO diaries (title, created_at)
|
VALUES ('2038-01-20 03:14:08', '2038-01-20 03:14:08');
|
-Warnings:
|
-Warning 1265 Data truncated for column 'created_at' at row 1
|
SELECT * FROM diaries;
|
id title created_at
|
1 2038-01-18 03:14:07 2038-01-18 03:14:07
|
-2 2038-01-20 03:14:08 1970-01-01 00:00:00
|
+2 2038-01-20 03:14:08 2038-01-20 03:14:08
|
DROP TABLE diaries;
|
|
|
Result length mismatch
|
|
|
mroonga/storage.column_datetime_32bit_before_unix_epoch w1 [ fail ]
|
Test ended at 2025-12-12 09:31:42
|
|
|
CURRENT_TEST: mroonga/storage.column_datetime_32bit_before_unix_epoch
|
--- /build/reproducible-path/mariadb-11.8.5/storage/mroonga/mysql-test/mroonga/storage/r/column_datetime_32bit_before_unix_epoch.result 2025-11-13 08:45:32.000000000 +0000
|
+++ /build/reproducible-path/mariadb-11.8.5/storage/mroonga/mysql-test/mroonga/storage/r/column_datetime_32bit_before_unix_epoch.reject 2025-12-12 09:31:42.262299498 +0000
|
@@ -6,9 +6,7 @@
|
) DEFAULT CHARSET UTF8;
|
INSERT IGNORE INTO diaries (title, created_at)
|
VALUES ('1000-01-01 00:00:00', '1000-01-01 00:00:00');
|
-Warnings:
|
-Warning 1265 Data truncated for column 'created_at' at row 1
|
SELECT * FROM diaries;
|
id title created_at
|
-1 1000-01-01 00:00:00 1970-01-01 00:00:00
|
+1 1000-01-01 00:00:00 1000-01-01 00:00:00
|
DROP TABLE diaries;
|
|
|
Result length mismatch
|
|
|
mroonga/storage.column_datetime_32bit_max w1 [ fail ]
|
Test ended at 2025-12-12 09:31:43
|
|
|
CURRENT_TEST: mroonga/storage.column_datetime_32bit_max
|
--- /build/reproducible-path/mariadb-11.8.5/storage/mroonga/mysql-test/mroonga/storage/r/column_datetime_32bit_max.result 2025-11-13 08:45:32.000000000 +0000
|
+++ /build/reproducible-path/mariadb-11.8.5/storage/mroonga/mysql-test/mroonga/storage/r/column_datetime_32bit_max.reject 2025-12-12 09:31:43.566403301 +0000
|
@@ -6,9 +6,7 @@
|
) DEFAULT CHARSET UTF8;
|
INSERT IGNORE INTO diaries (title, created_at)
|
VALUES ('9999-12-31 23:59:59', '9999-12-31 23:59:59');
|
-Warnings:
|
-Warning 1265 Data truncated for column 'created_at' at row 1
|
SELECT * FROM diaries;
|
id title created_at
|
-1 9999-12-31 23:59:59 1970-01-01 00:00:00
|
+1 9999-12-31 23:59:59 9999-12-31 23:59:59
|
DROP TABLE diaries;
|
|
|
Result length mismatch
|
Filing this as priority 'minor' as x32 is a very marginal architecture. Nevertheless this shows that the Mroonga code date handling isn't as robuts as elsewhere in MariaDB.
Attachments
Issue Links
- relates to
-
MDEV-32188 make TIMESTAMP use whole 32-bit unsigned range
-
- Closed
-
-
MDEV-9270 mroonga datetime test fails on arch alpha
-
- Closed
-