Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Won't Fix
-
10.1
-
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.