[MDEV-19368] rpl.rpl_get_lock, main.dirty_close, main.loaddata, rpl.rpl_test_framework, main.flush fail in buildbot on ASAN build with mysqltest failed but provided no output Created: 2019-04-30  Updated: 2023-11-29  Resolved: 2023-11-29

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.1
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Oleksandr Byelkin
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-asan/builds/1089/steps/mtr_nm/logs/stdio

10.1 5b035c84

rpl.rpl_get_lock 'mix'                   w4 [ fail ]
        Test ended at 2019-04-30 09:10:17
 
CURRENT_TEST: rpl.rpl_get_lock
 
 
mysqltest failed but provided no output
The result from queries just before the failure was:
< snip >
1
select * from t1;
n
1
select is_free_lock("lock"), is_used_lock("lock") = connection_id();
is_free_lock("lock")	is_used_lock("lock") = connection_id()
0	1
explain extended select is_free_lock("lock"), is_used_lock("lock");
id	select_type	table	type	possible_keys	key	key_len	ref	rows	filtered	Extra
1	SIMPLE	NULL	NULL	NULL	NULL	NULL	NULL	NULL	NULL	No tables used
Warnings:
Note	1003	select is_free_lock('lock') AS `is_free_lock("lock")`,is_used_lock('lock') AS `is_used_lock("lock")`
select is_free_lock("lock2");
is_free_lock("lock2")
1
select is_free_lock(NULL);
is_free_lock(NULL)
NULL
drop table t1;
include/rpl_end.inc

Note: Previously similar failures turned out to be memory leaks detected by LeakSanitizer, which would make the test fail at the end, but since there was no result mismatch or detectable warnings/errors in the error log, MTR would produce this (admittedly confusing) message. It could be the case here as well, or maybe not.



 Comments   
Comment by Elena Stepanova [ 2019-04-30 ]

http://buildbot.askmonty.org/buildbot/builders/kvm-asan/builds/871

main.loaddata                            w3 [ fail ]
        Test ended at 2019-04-11 06:42:33
 
CURRENT_TEST: main.loaddata
 
 
mysqltest failed but provided no output
The result from queries just before the failure was:
< snip >
CREATE VIEW v2 AS SELECT * FROM v1;
LOAD DATA INFILE '../../std_data/loaddata7.dat' INTO TABLE v1
FIELDS TERMINATED BY ',' LINES TERMINATED BY '\r\n';
ERROR HY000: Incorrect usage of Multi-table VIEW and LOAD
LOAD DATA INFILE '../../std_data/loaddata7.dat' INTO TABLE v2
FIELDS TERMINATED BY ',' LINES TERMINATED BY '\r\n';
ERROR HY000: Incorrect usage of Multi-table VIEW and LOAD
DROP VIEW IF EXISTS v2,v1;
DROP TABLE IF EXISTS t1,t0;
CREATE TABLE t1 (a INT, b INT, PRIMARY KEY (a), UNIQUE(b));
INSERT INTO t1 VALUES (1,1);
CREATE TABLE t2 (c INT);
CREATE VIEW v AS SELECT t1.* FROM t1 JOIN t2;
SELECT a, b FROM t1 INTO OUTFILE '15645.data';
LOAD DATA INFILE '15645.data' IGNORE INTO TABLE v (a,b);
ERROR HY000: Incorrect usage of Multi-table VIEW and LOAD
LOAD DATA INFILE '15645.data' REPLACE INTO TABLE v (a,b);
ERROR HY000: Incorrect usage of Multi-table VIEW and LOAD
drop table t1,t2;
drop view v;

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