[MDEV-8841] innodb_zip.innodb-create-options fails in buildbot Created: 2015-09-24 Updated: 2017-01-27 Resolved: 2015-09-24 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Tests |
| Affects Version/s: | 5.5 |
| Fix Version/s: | 5.5.46 |
| Type: | Bug | Priority: | Major |
| Reporter: | Elena Stepanova | Assignee: | Elena Stepanova |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||
| Description |
|
http://buildbot.askmonty.org/buildbot/builders/work-amd64-valgrind/builds/7594/steps/test/logs/stdio
It fails on a valgrind build, but without valgrind errors. |
| Comments |
| Comment by Elena Stepanova [ 2015-09-24 ] | ||||||||||||||
|
The reason of the problem is this: So, test1 does the proper cleanup, but mysql.proc remains open. In our case, test1 is innodb.innodb_notembedded (but it can really be any test which does something with a system table), test2 is innodb.xa_recovery, and test3 is innodb_zip.innodb-create-options which is reported to be failed, but again it could be any other test as well.
Thus, the only suitable place to fix it is in xa_recovery. The least intrusive solution that I see is to add FLUSH TABLES at the beginning of the test. It does not contradict the test logic, but remains previous influences. | ||||||||||||||
| Comment by Elena Stepanova [ 2015-09-24 ] | ||||||||||||||
|
https://github.com/MariaDB/server/commit/dca4ab92b8e32ae1abe54666cf2313d94d5804a4 |