percona_status_wait_query_cache_mutex test does not restore the pre-test state
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Fix Released
|
Undecided
|
Unassigned | ||
5.1 |
Fix Released
|
Undecided
|
Oleg Tsarev |
Bug Description
This is probably introduced by the fix to bug 878709. It looks like DEBUG_SYNC state is not properly reset at the end of the testcase.
http://
main.percona_
MTR's internal check of the test case 'main.percona_
This means that the test case does not preserve the state that existed
before the test case was executed. Most likely the test case did not
do a proper clean-up. It could also be caused by the previous test run
by this thread, if the server wasn't restarted.
This is the diff of the states of the servers before and after the
test case was executed:
mysqltest: Logging to '/home/
mysqltest: Results saved in '/home/
mysqltest: Connecting to server localhost:13010 (socket /tmp/lPd7JrZxVa
mysqltest: ... Connected.
mysqltest: Start processing test commands from './include/
mysqltest: ... Done processing test commands.
--- /home/jenkins/
+++ /home/jenkins/
@@ -28,7 +28,7 @@
DATETIME_FORMAT %Y-%m-%d %H:%i:%s
DATE_FORMAT %Y-%m-%d
DEBUG
-DEBUG_SYNC ON - current signal: ''
+DEBUG_SYNC ON - current signal: 'unlock_mutex'
DEFAULT_
DELAYED_
DELAYED_
mysqltest: Result content mismatch
not ok
Related branches
- Laurynas Biveinis (community): Approve
-
Diff: 17 lines (+2/-0)2 files modifiedPercona-Server/mysql-test/r/percona_status_wait_query_cache_mutex.result (+1/-0)
Percona-Server/mysql-test/t/percona_status_wait_query_cache_mutex.test (+1/-0)
Changed in percona-server: | |
status: | New → In Progress |
Changed in percona-server: | |
status: | In Progress → Fix Committed |
http:// jenkins. percona. com/view/ Percona% 20Server% 205.1/job/ percona- server- 5.1-param/ 228/BUILD_ TYPE=release, Host=centos5- 64/testReport/ junit/( root)/main/ percona_ slow_extended_ error_on_ quit/