[MDEV-12055] binlog.binlog_stm_ctype_ucs test failing Created: 2017-02-13  Updated: 2021-09-06  Resolved: 2017-05-05

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.2.4
Fix Version/s: 10.2.5, 10.3.0

Type: Bug Priority: Major
Reporter: Daniel Black Assignee: Alexander Barkov
Resolution: Fixed Votes: 0
Labels: contribution, foundation, patch
Environment:

ubuntu 16.04 ppc64le

Issue Links:
Relates
relates to MDEV-7069 Fix buildbot failures in main server ... Stalled
relates to MDEV-10866 Extend PREPARE and EXECUTE IMMEDIATE ... Closed

 Description   

f04efa839dd0288396f88c4a1d63e1d599573ace commit on 10.2 branch

Seems the previous attempt at fixing this wasn't universal.

binlog.binlog_stm_ctype_ucs

binlog.binlog_stm_ctype_ucs 'mix'        w22 [ fail ]
 
        Test ended at 2017-02-13 10:57:38
 
 
 
CURRENT_TEST: binlog.binlog_stm_ctype_ucs
 
--- /home/danielgb/mariadb/mysql-test/suite/binlog/r/binlog_stm_ctype_ucs.result        2017-02-13 10:57:17.286362101 +1100
 
+++ /home/danielgb/mariadb/mysql-test/suite/binlog/r/binlog_stm_ctype_ucs.reject        2017-02-13 10:57:38.590814811 +1100
 
@@ -76,21 +76,21 @@
 
 /*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
 
 DELIMITER /*!*/;
 
 # at #
 
-#700101  6:46:40 server id #  end_log_pos # CRC32 XXX  Start: binlog v 4, server v #.##.## created 700101  6:46:40
 
+#170213 10:57:38 server id #  end_log_pos # CRC32 XXX  Start: binlog v 4, server v #.##.## created 170213 10:57:38
 
 # at #
 
-#700101  6:46:40 server id #  end_log_pos # CRC32 XXX  Gtid list [#-#-#]
 
+#170213 10:57:38 server id #  end_log_pos # CRC32 XXX  Gtid list [#-#-#]
 
 # at #
 
-#700101  6:46:40 server id #  end_log_pos # CRC32 XXX  Binlog checkpoint master-bin.000002
 
+#170213 10:57:38 server id #  end_log_pos # CRC32 XXX  Binlog checkpoint master-bin.000002
 
 # at #
 
-#700101  6:46:40 server id #  end_log_pos # CRC32 XXX  Binlog checkpoint master-bin.000003
 
+#170213 10:57:38 server id #  end_log_pos # CRC32 XXX  Binlog checkpoint master-bin.000003
 
 # at #
 
-#700101  6:46:40 server id #  end_log_pos # CRC32 XXX  GTID #-#-# ddl
 
+#170213 10:57:38 server id #  end_log_pos # CRC32 XXX  GTID #-#-# ddl
 
 /*!100101 SET @@session.skip_parallel_replication=0*//*!*/;
 
 /*!100001 SET @@session.gtid_domain_id=#*//*!*/;
 
 /*!100001 SET @@session.server_id=#*//*!*/;
 
 /*!100001 SET @@session.gtid_seq_no=#*//*!*/;
 
 # at #
 
-#700101  6:46:40 server id #  end_log_pos # CRC32 XXX  Query   thread_id=#     exec_time=#     error_code=0
 
+#170213 10:57:38 server id #  end_log_pos # CRC32 XXX  Query   thread_id=#     exec_time=#     error_code=0
 
 use `test`/*!*/;
 
 SET TIMESTAMP=XXX/*!*/;
 
 SET @@session.pseudo_thread_id=#/*!*/;
 
@@ -104,105 +104,105 @@
 
 CREATE TABLE t1 (a VARCHAR(10) CHARACTER SET utf8)
 
 /*!*/;
 
 # at #
 
-#700101  6:46:40 server id #  end_log_pos # CRC32 XXX  GTID #-#-#
 
+#170213 10:57:38 server id #  end_log_pos # CRC32 XXX  GTID #-#-#
 
 /*!100001 SET @@session.gtid_seq_no=#*//*!*/;
 
...
 
...
 
...
 
binlog.binlog_row_ctype_ucs 'row'        w21 [ fail ]
 
        Test ended at 2017-02-13 10:57:38
 
 
 
CURRENT_TEST: binlog.binlog_row_ctype_ucs
 
--- /home/danielgb/mariadb/mysql-test/suite/binlog/r/binlog_row_ctype_ucs.result        2017-02-13 10:57:17.286362101 +1100
 
+++ /home/danielgb/mariadb/mysql-test/suite/binlog/r/binlog_row_ctype_ucs.reject        2017-02-13 10:57:38.642815916 +1100
 
@@ -72,21 +72,21 @@
 
 /*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
 
 DELIMITER /*!*/;
 
 # at #
 
-#700101  6:46:40 server id #  end_log_pos # CRC32 XXX  Start: binlog v 4, server v #.##.## created 700101  6:46:40
 
+#170213 10:57:38 server id #  end_log_pos # CRC32 XXX  Start: binlog v 4, server v #.##.## created 170213 10:57:38
 
...
 
..
 
...



 Comments   
Comment by Alexander Barkov [ 2017-02-14 ]

Daniel, I cannot reproduce the problem with the latest 10.2 source, d731ce21a7bc25a49958789d24b3f0eec5845aea.
Can you try with the latest sources?

Which build options and mtr options did you use? Did it happen on your box, or on some build bot machine?
What is the OS?

Thanks!

Comment by Daniel Black [ 2017-02-14 ]

OS as per environment - ubuntu 16.04 - ppc64le

repeatable in build environment and stand alone as below.

danielgb@p82:~/mariadb$ git status
 
On branch 10.2
 
Your branch is up-to-date with 'origin/10.2'.
 
nothing to commit, working directory clean
 
danielgb@p82:~/mariadb$ git show
 
commit 8877f1c32566b32bf9c598052e8f866a361190fb
 
Author: Vladislav Vaintroub <wlad@mariadb.com>
 
Date:   Tue Feb 14 18:07:42 2017 +0100
 
 
 
danielgb@p82:~/build_mariadb$ echo $CXX  , $CC
 
/opt/at9.0/bin/g++ , /opt/at9.0/bin/gcc
 
danielgb@p82:~/build_mariadb$ cmake ../mariadb/  -DDOWNLOAD_BOOST=1 -DWITH_BOOST=${HOME}/build_boost -DCMAKE_C_COMPILER=${CC:-gcc}  -DCMAKE_CXX_COMPILER=${CXX:-g++} -DCMAKE_C_FLAGS_RELWITHDEBINFO="-O3 -g"  -DCMAKE_CXX_FLAGS_RELWITHDEBINFO="-O3 -g" -DWITH_SSL=system -DCMAKE_INSTALL_PREFIX=/usr/local/mariadb-10.2
 
-- Running cmake version 3.5.1
 
-- The C compiler identification is GNU 5.3.1
 
-- The CXX compiler identification is GNU 5.3.1
 
-- Check for working C compiler: /opt/at9.0/bin/gcc
 
-- Check for working C compiler: /opt/at9.0/bin/gcc -- works
 
-- Detecting C compiler ABI info
 
-- Detecting C compiler ABI info - done
 
-- Detecting C compile features
 
-- Detecting C compile features - done
 
-- Check for working CXX compiler: /opt/at9.0/bin/g++
 
-- Check for working CXX compiler: /opt/at9.0/bin/g++ -- works
 
-- Detecting CXX compiler ABI info
 
-- Detecting CXX compiler ABI info - done
 
..
 
make -j 50
 
..
 
danielgb@p82:~/build_mariadb$ (cd mysql-test/ ; ./mtr  binlog.binlog_stm_ctype_ucs   )                                                 
Logging: /home/danielgb/mariadb/mysql-test/mysql-test-run.pl  binlog.binlog_stm_ctype_ucs
 
vardir: /home/danielgb/build_mariadb/mysql-test/var
 
Removing old var directory...
 
Creating var directory '/home/danielgb/build_mariadb/mysql-test/var'...
 
 - symlinking 'var' to '/run/shm/var_auto_UMZk'
 
Checking supported features...
 
2017-02-15  8:13:02 70367108500592 [Note] options --log-slow-admin-statements, --log-queries-not-using-indexes and --log-slow-slave-statements have no effect if --log_slow_queries is not set
 
MariaDB Version 10.2.4-MariaDB
 
 - SSL connections supported
 
Collecting tests...
 
Installing system database...
 
worker[2] Using MTR_BUILD_THREAD 300, with reserved ports 16000..16019
 
worker[1] Using MTR_BUILD_THREAD 301, with reserved ports 16020..16039
 
worker[3] Using MTR_BUILD_THREAD 302, with reserved ports 16040..16059
 
worker[4] Using MTR_BUILD_THREAD 303, with reserved ports 16060..16079
 
worker[9] Using MTR_BUILD_THREAD 304, with reserved ports 16080..16099
 
worker[13] Using MTR_BUILD_THREAD 305, with reserved ports 16100..16119
 
worker[12] Using MTR_BUILD_THREAD 306, with reserved ports 16120..16139
 
worker[5] Using MTR_BUILD_THREAD 308, with reserved ports 16160..16179
 
worker[8] Using MTR_BUILD_THREAD 307, with reserved ports 16140..16159
 
worker[11] Using MTR_BUILD_THREAD 311, with reserved ports 16220..16239
 
worker[10] Using MTR_BUILD_THREAD 309, with reserved ports 16180..16199
 
worker[21] Using MTR_BUILD_THREAD 314, with reserved ports 16280..16299
 
worker[16] Using MTR_BUILD_THREAD 315, with reserved ports 16300..16319
 
worker[18] Using MTR_BUILD_THREAD 317, with reserved ports 16340..16359
 
worker[14] Using MTR_BUILD_THREAD 316, with reserved ports 16320..16339
 
worker[6] Using MTR_BUILD_THREAD 312, with reserved ports 16240..16259
 
worker[7] Using MTR_BUILD_THREAD 310, with reserved ports 16200..16219
 
worker[15] Using MTR_BUILD_THREAD 313, with reserved ports 16260..16279
 
worker[20] Using MTR_BUILD_THREAD 318, with reserved ports 16360..16379
 
worker[19] Using MTR_BUILD_THREAD 320, with reserved ports 16400..16419
 
worker[28] Using MTR_BUILD_THREAD 324, with reserved ports 16480..16499
 
worker[24] Using MTR_BUILD_THREAD 322, with reserved ports 16440..16459
 
worker[22] Using MTR_BUILD_THREAD 319, with reserved ports 16380..16399
 
worker[25] Using MTR_BUILD_THREAD 323, with reserved ports 16460..16479
 
worker[23] Using MTR_BUILD_THREAD 321, with reserved ports 16420..16439
 
worker[33] Using MTR_BUILD_THREAD 326, with reserved ports 16520..16539
 
worker[17] Using MTR_BUILD_THREAD 327, with reserved ports 16540..16559
 
worker[32] Using MTR_BUILD_THREAD 325, with reserved ports 16500..16519
 
worker[27] Using MTR_BUILD_THREAD 328, with reserved ports 16560..16579
 
 
 
worker[30] Using MTR_BUILD_THREAD 329, with reserved ports 16580..16599
 
==============================================================================
 
 
 
TEST                                  WORKER RESULT   TIME (ms) or COMMENT
 
--------------------------------------------------------------------------
 
 
 
worker[26] Using MTR_BUILD_THREAD 332, with reserved ports 16640..16659
 
worker[29] Using MTR_BUILD_THREAD 331, with reserved ports 16620..16639
 
worker[31] Using MTR_BUILD_THREAD 330, with reserved ports 16600..16619
 
worker[34] Using MTR_BUILD_THREAD 333, with reserved ports 16660..16679
 
worker[35] Using MTR_BUILD_THREAD 334, with reserved ports 16680..16699
 
worker[36] Using MTR_BUILD_THREAD 335, with reserved ports 16700..16719
 
worker[44] Using MTR_BUILD_THREAD 338, with reserved ports 16760..16779
 
worker[45] Using MTR_BUILD_THREAD 336, with reserved ports 16720..16739
 
worker[43] Using MTR_BUILD_THREAD 339, with reserved ports 16780..16799
 
worker[39] Using MTR_BUILD_THREAD 337, with reserved ports 16740..16759
 
worker[42] Using MTR_BUILD_THREAD 340, with reserved ports 16800..16819
 
worker[40] Using MTR_BUILD_THREAD 341, with reserved ports 16820..16839
 
worker[38] Using MTR_BUILD_THREAD 344, with reserved ports 16880..16899
 
worker[37] Using MTR_BUILD_THREAD 342, with reserved ports 16840..16859
 
worker[47] Using MTR_BUILD_THREAD 343, with reserved ports 16860..16879
 
worker[46] Using MTR_BUILD_THREAD 345, with reserved ports 16900..16919
 
worker[50] Using MTR_BUILD_THREAD 346, with reserved ports 16920..16939
 
worker[49] Using MTR_BUILD_THREAD 310, with reserved ports 16200..16219
 
worker[41] Using MTR_BUILD_THREAD 347, with reserved ports 16940..16959
 
worker[48] Using MTR_BUILD_THREAD 314, with reserved ports 16280..16299
 
binlog.binlog_stm_ctype_ucs 'row'        w20 [ skipped ]  Neither MIXED nor STATEMENT binlog format
 
binlog.binlog_stm_ctype_ucs 'stmt'       w16 [ fail ]
 
        Test ended at 2017-02-15 08:13:05
 
 
 
CURRENT_TEST: binlog.binlog_stm_ctype_ucs
 
--- /home/danielgb/mariadb/mysql-test/suite/binlog/r/binlog_stm_ctype_ucs.result        2017-02-13 13:11:28.594707456 +1100
 
+++ /home/danielgb/mariadb/mysql-test/suite/binlog/r/binlog_stm_ctype_ucs.reject        2017-02-15 08:13:05.371193987 +1100
 
@@ -76,21 +76,21 @@
 
 /*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
 
 DELIMITER /*!*/;
 
 # at #
 
-#700101  6:46:40 server id #  end_log_pos # CRC32 XXX  Start: binlog v 4, server v #.##.## created 700101  6:46:40
 
+#170215  8:13:05 server id #  end_log_pos # CRC32 XXX  Start: binlog v 4, server v #.##.## created 170215  8:13:05
 
 # at #
 
-#700101  6:46:40 server id #  end_log_pos # CRC32 XXX  Gtid list [#-#-#]
 
+#170215  8:13:05 server id #  end_log_pos # CRC32 XXX  Gtid list [#-#-#]
 
 # at #
 
-#700101  6:46:40 server id #  end_log_pos # CRC32 XXX  Binlog checkpoint master-bin.000002
 
+#170215  8:13:05 server id #  end_log_pos # CRC32 XXX  Binlog checkpoint master-bin.000002
 
....
 
danielgb@p82:~/build_mariadb$ env | grep MTR
 
MTR_PARALLEL=50
 
MTR_MEM=1
 
MTR_PARALLEL_MAX=190
 
danielgb@p82:~/build_mariadb$ date --rfc-2822
 
Wed, 15 Feb 2017 08:15:05 +1100

Using OS gcc/g++ (5.4.1) achieved same result.

x86_64 fedora 24 laptop generates same results. I suspect the time-zone (though obviously glossed over this in the solution).

Comment by Daniel Black [ 2021-09-06 ]

Obviously timezone/test time dependent.

https://github.com/MariaDB/server/commit/38648bbbf53124a0d04047162f67528729b909b5 fixes it for the remaining 4 hours of the day - 20:00 -> 23:59 from https://bugs.gentoo.org/807995

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