[MDEV-33013] versioning.insert2 fails on 32-bit with wrong result Created: 2023-12-13  Updated: 2023-12-19  Resolved: 2023-12-19

Status: Closed
Project: MariaDB Server
Component/s: Temporal Types, Tests
Affects Version/s: N/A
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Elena Stepanova Assignee: Michael Widenius
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Problem/Incident
is caused by MDEV-32188 make TIMESTAMP use whole 32-bit unsig... In Testing

 Description   

https://buildbot.mariadb.net/buildbot/builders/kvm-fulltest2/builds/43443

bb-11.3-timestamp fd6689da3fffc4d57d8ebde5f8776aefa8cdb8a4

 
versioning.insert2 'innodb'              w1 [ fail ]
 
        Test ended at 2023-10-25 02:49:56
 
 
 
...
 
25 02:49:56.457234136 -0400
 
@@ -68,7 +68,7 @@
 
 insert into t1 values (1, null, null, 'foo');
 
 select i, c,  e>LEFT(SYS_TIME_MAX, 10) AS current_row from t1;;
 
 i	c	current_row
 
-1	foo	1
 
+1	foo	0
 
 drop table t1;
 
 drop table t2;
 
 #
 
 
 
mysqltest: Result content mismatch



 Comments   
Comment by Michael Widenius [ 2023-12-15 ]

I was not not able to repeat this one 32 bit build.
I have updated the test to use @@time_zone="+00:00" to see if this fixes this issue.

Comment by Michael Widenius [ 2023-12-19 ]

Fixed in bb-10.4-timestamp

Generated at Thu Feb 08 10:35:44 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.