Test main.type_temporal_fractional is unstable

Bug #1673800 reported by Laurynas Biveinis on 2017-03-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona Server moved to https://jira.percona.com/projects/PS
Status tracked in 5.7
5.5
Invalid
Undecided
Unassigned
5.6
Fix Released
Low
Laurynas Biveinis
5.7
Fix Released
Low
Laurynas Biveinis

Bug Description

On 5.6 trunk:

main.type_temporal_fractional w1 [ fail ]
        Test ended at 2017-03-14 09:45:32

CURRENT_TEST: main.type_temporal_fractional
--- /mnt/workspace/percona-server-5.6-trunk/BUILD_TYPE/debug/Host/ubuntu-precise-64bit/mysql-test/r/type_temporal_fractional.result 2017-03-08 15:06:33.345662559 +0300
+++ /mnt/workspace/percona-server-5.6-trunk/BUILD_TYPE/debug/Host/ubuntu-precise-64bit/build/mysql-test/var/1/log/type_temporal_fractional.reject 2017-03-14 16:45:32.192047323 +0300
@@ -15911,6 +15911,7 @@
 WHERE col_time_2_not_null = GREATEST(CURRENT_DATE(),col_timestamp_6_key)
 ORDER BY 1;
 c1
+2017-03-14 16:45:31.47000
 DROP TABLE t1;
 SET @@time_zone='+00:00';
 CREATE TABLE t1 (col_datetime_4_not_null DATETIME(4) NOT NULL);

mysqltest: Result content mismatch

Tags: ci Edit Tag help
tags: added: ci

Added asserts and confirmed that the failure happens when CURRENT_TIMESTAMP at INSERT time happens to have four trailing zeroes in microseconds, comparing equal to TIME(2) column.

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-2247

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers