Details
-
Bug
-
Status: Closed (View Workflow)
-
Trivial
-
Resolution: Won't Fix
-
10.1, 10.2
-
None
Description
jp.jp_charset_sjis 'innodb_plugin' [ fail ]
|
Test ended at 2016-10-10 16:57:18
|
|
|
CURRENT_TEST: jp.jp_charset_sjis
|
mysqltest: At line 40: query 'LOAD DATA LOCAL INFILE 'suite/jp/std_data/jisx0201_sjis.dat' INTO TABLE `�s�P`' failed: 1290: The MariaDB server is running with the --secure-file-priv option so it cannot execute this statement
|
|
|
The result from queries just before the failure was:
|
< snip >
|
drop table if exists `�s�W`;
|
drop table if exists `�s�X`;
|
SET NAMES sjis;
|
SET character_set_database = sjis;
|
CREATE TABLE `�s�P` (`�b�P` char(20)) DEFAULT CHARSET = sjis engine = innodb;
|
CREATE TABLE `�s�Q` (`�b�P` char(20)) DEFAULT CHARSET = sjis engine = innodb;
|
CREATE TABLE `�s�R` (`�b�P` char(20)) DEFAULT CHARSET = sjis engine = innodb;
|
CREATE TABLE `�s�S` (`�b�P` char(20)) DEFAULT CHARSET = sjis engine = myisam;
|
CREATE TABLE `�s�T` (`�b�P` char(20)) DEFAULT CHARSET = sjis engine = myisam;
|
CREATE TABLE `�s�U` (`�b�P` char(20)) DEFAULT CHARSET = sjis engine = myisam;
|
CREATE TABLE `�s�V` (`�b�P` char(20)) DEFAULT CHARSET = sjis engine = MEMORY;
|
CREATE TABLE `�s�W` (`�b�P` char(20)) DEFAULT CHARSET = sjis engine = MEMORY;
|
CREATE TABLE `�s�X` (`�b�P` char(20)) DEFAULT CHARSET = sjis engine = MEMORY;
|
LOAD DATA LOCAL INFILE 'suite/jp/std_data/jisx0201_sjis.dat' INTO TABLE `�s�P`;
|
|
|
More results from queries before failure can be found in /data/src/10.1-bug3/mysql-test/var/log/jp_charset_sjis.log
|
safe_mutex: Found wrong usage of mutex 'LOCK_thread_count' and 'LOCK_status'
|
Mutex currently locked (in reverse order):
|
LOCK_status /data/src/10.1-bug3/libmysqld/../sql/sql_class.h line 3872
|
LOCK_thread_count /data/src/10.1-bug3/libmysqld/lib_sql.cc line 432
|
jp.jp_charset_sjis
|
jp.jp_charset_ujis
|
jp.jp_charset_utf8
|
jp.jp_convert_sjis
|
jp.jp_convert_ujis
|
jp.jp_convert_utf8
|
jp.jp_like_sjis
|
jp.jp_like_ujis
|
jp.jp_like_utf8
|
jp.jp_select_sjis
|
...
|
TokuDB tests produce various result mismatches.