Intermittent testcase check warning on innodb_stress.innodb_hugestress_blob
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS | Status tracked in 5.7 | |||||
5.5 |
Invalid
|
Undecided
|
Unassigned | |||
5.6 |
Fix Released
|
Low
|
Laurynas Biveinis | |||
5.7 |
Fix Released
|
Low
|
Laurynas Biveinis |
Bug Description
On 5.6 trunk:
innodb_
MTR's internal check of the test case 'innodb_
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 '/mnt/workspace
mysqltest: Results saved in '/mnt/workspace
mysqltest: Connecting to server localhost:13031 (socket /tmp/m_
mysqltest: ... Connected.
mysqltest: Start processing test commands from './include/
mysqltest: ... Done processing test commands.
--- /mnt/workspace/
+++ /mnt/workspace/
@@ -297,7 +297,7 @@
INNODB_
INNODB_
INNODB_
-INNODB_
+INNODB_
INNODB_
INNODB_STRICT_MODE OFF
INNODB_SUPPORT_XA ON
mysqltest: Result content mismatch
The testcase itself does not enable innodb_
tags: | added: ci upstream |
https:/ /github. com/percona/ percona- server/ pull/1348 /github. com/percona/ percona- server/ pull/1349
https:/