Details
Minor Description
http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/9567/steps/test_2/logs/stdio
innodb.purge_thread_shutdown 'innodb' w4 [ fail ]
|
Test ended at 2017-09-13 01:37:34
|
|
|
CURRENT_TEST: innodb.purge_thread_shutdown
|
--- /mnt/buildbot/build/mariadb-10.2.9/mysql-test/suite/innodb/r/purge_thread_shutdown.result 2017-09-13 00:04:28.000000000 +0300
|
+++ /mnt/buildbot/build/mariadb-10.2.9/mysql-test/suite/innodb/r/purge_thread_shutdown.reject 2017-09-13 01:37:33.000000000 +0300
|
@@ -5,11 +5,11 @@
|
select user,state from information_schema.processlist order by 2;
|
user state
|
root
|
+system user closing tables
|
root Filling schema table
|
system user InnoDB purge coordinator
|
system user InnoDB purge worker
|
system user InnoDB purge worker
|
-system user InnoDB purge worker
|
system user InnoDB shutdown handler
|
set global debug_dbug='+d,only_kill_system_threads';
|
set global innodb_fast_shutdown=0;
|
|
|
mysqltest: Result length mismatch
|
Attachments
Activity
Pushed to 10.4.
(Marko removed the test from 10.5, as it is no longer meaningful there.)
From Zulip discussions:
The test wants to show the list of running processes, to show which system threads and connection threads are running.
The problem is that using the state to identify the thread doesn't work, as it changes as the thread is doing stuff (enter_state()). I would suggest to change the query to SELECT user FROM information_schema.processlist order by 1, this way the user-vs-system threads can be seen which I think is good enough.
Or alternatively, include/wait_condition.inc with some condition that counts each kind of thread and compares with expected count. That would be equivalent, but not sure if that complexity is needed