Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.2(EOL)
-
None
Description
main.show_explain_ps w3 [ fail ]
|
Test ended at 2016-07-03 18:36:27
|
|
|
CURRENT_TEST: main.show_explain_ps
|
--- /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/r/show_explain_ps.result 2016-07-03 15:54:00.100512059 -0400
|
+++ /home/buildbot/maria-slave/power8-vlp03-bintar-debug/build/mysql-test/r/show_explain_ps.reject 2016-07-03 18:36:27.201444865 -0400
|
@@ -31,5 +31,4 @@
|
from performance_schema.events_waits_history_long
|
where event_name='wait/synch/cond/sql/show_explain';
|
event_name
|
-wait/synch/cond/sql/show_explain
|
drop table t0;
|
|
|
mysqltest: Result length mismatch
|
Attachments
Issue Links
- blocks
-
MDEV-7069 Fix buildbot failures in main server trees
-
- Closed
-
Activity
Ok, this seems to be a race condition in the test.
Test setup:
- The target thread is stopped in doing a busy-wait in dbug_serve_apcs()
- The SHOW EXPLAIN thread makes an "APC call" in Apc_target::make_apc_call
Looking in the code: in Apc_target::make_apc_call we do
1. Put an APC request into the target's queue
2. while (!processed)
The "wait/synch/cond/sql/show_explain" wait happens on step#2.
The test can fail when the following happens:
show_explain_thread> Step#1: Put an APC request into the target's queue
target_query_thread> process the request
target_query_thread> request->processed= true
show_explain_thread> Step#2: oh, processed==true, no need to wait.
Fails rather reliably on fulltest2.