[MDEV-9363] Mroonga tests with datetime field fail on Solaris in buildbot Created: 2016-01-05  Updated: 2021-11-09  Resolved: 2021-11-09

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - Mroonga, Temporal Types, Tests
Affects Version/s: 10.1
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Nayuta Yanagisawa (Inactive)
Resolution: Won't Fix Votes: 0
Labels: buildbot
Environment:

Solaris 10 x86


Issue Links:
Blocks
blocks MDEV-7069 Fix buildbot failures in main server ... Stalled
Sprint: 10.2.1-5, 10.1.15

 Description   

http://buildbot.askmonty.org/buildbot/builders/sol10-64/builds/4611/steps/test/logs/stdio

CURRENT_TEST: mroonga/storage.column_datetime_64bit_before_unix_epoch
--- /export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.1.10/storage/mroonga/mysql-test/mroonga/storage/r/column_datetime_64bit_before_unix_epoch.result	2015-12-30 15:03:39.000000000 -0500
+++ /export/home/buildbot/maria-slave/solaris10-x86/build/mariadb-10.1.10/storage/mroonga/mysql-test/mroonga/storage/r/column_datetime_64bit_before_unix_epoch.reject	2015-12-31 02:44:06.881358000 -0500
@@ -16,5 +16,5 @@
 VALUES ('1000-01-01 00:00:00', '1000-01-01 00:00:00');
 SELECT * FROM diaries;
 id	title	created_at
-1	1000-01-01 00:00:00	1000-01-01 00:00:00
+1	1000-01-01 00:00:00	1000-01-02 00:00:00
 DROP TABLE diaries;

There are more failing tests, but apparently the mismatch is always the same – the value is inserted as '1000-01-01 00:00:00', but returned as '1000-01-02 00:00:00'.



 Comments   
Comment by Sergey Vojtovich [ 2016-06-28 ]

serg, please review workaround for this bug.

Comment by Sergei Golubchik [ 2016-07-08 ]

Ok to push. But don't close the bug, please. Reassign it to Kentoku, so that we could track this as an upstream bug.

Comment by Nayuta Yanagisawa (Inactive) [ 2021-11-09 ]

We do not build on Solaris anymore. So, I will close the issue.

Generated at Thu Feb 08 07:34:06 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.