Details
Description
http://askmonty.org/buildbot/builders/xenial-amd64-valgrind/builds/247
funcs_2.innodb_charset 'xtradb' w10 [ fail ] timeout after 9000 seconds
|
Test ended at 2017-01-01 13:06:09
|
|
Test case timeout after 9000 seconds
|
|
== /dev/shm/var/10/log/innodb_charset.log ==
|
DFB7 1
|
DFB8 1
|
DFB9 1
|
DFBA 1
|
DFBB 1
|
DFBC 1
|
DFBD 1
|
DFBE 1
|
DFBF 1
|
DROP TABLE IF EXISTS test.t1;
|
DROP TABLE IF EXISTS test.t1;
|
DROP DATABASE test;
|
CREATE DATABASE test CHARACTER SET utf8;
|
USE test;
|
CREATE TABLE test.t1 (a CHAR(4) CHARACTER SET utf8 COLLATE utf8_slovak_ci) ENGINE=InnoDB CHARACTER SET utf8 COLLATE utf8_slovak_ci;
|
SHOW TABLE STATUS LIKE 't1';
|
Name Engine Version Row_format Rows Avg_row_length Data_length Max_data_length Index_length Data_free Auto_increment Create_time Update_time Check_time Collation Checksum Create_options Comment
|
t1 InnoDB # # # # # # # # # # # # utf8_slovak_ci # # #
|
LOAD DATA INFILE
|
'MYSQL_TEST_DIR/suite/funcs_2/data/charset_utf8.txt' INTO TABLE test.t1;
|
The test reaches different places before the timeout, it doesn't look like it gets stuck, it's just really slow with valgrind. Even without parallel execution, it takes ~45 min for each combination (as opposed to ~25 seconds without valgrind). And with high levels of parallel execution it exceeds 9000 seconds timeout as shown above
Attachments
Issue Links
- relates to
-
MDEV-7069 Fix buildbot failures in main server trees
- Stalled