Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Won't Fix
-
10.2
-
None
Description
There are no logs for the failure at the moment. The output looks like this:
sys_vars.innodb_buffer_pool_dump_at_shutdown_basic 'innodb' w2 [ fail ]
|
Test ended at 2017-08-05 01:05:04
|
|
CURRENT_TEST: sys_vars.innodb_buffer_pool_dump_at_shutdown_basic
|
mysqltest: At line 42: command "file_exists" failed with error: 1 my_errno: 175 errno: 2
|
|
The result from queries just before the failure was:
|
< snip >
|
@orig
|
1
|
SET GLOBAL innodb_buffer_pool_dump_at_shutdown = OFF;
|
SELECT @@global.innodb_buffer_pool_dump_at_shutdown;
|
@@global.innodb_buffer_pool_dump_at_shutdown
|
0
|
SET GLOBAL innodb_buffer_pool_dump_at_shutdown = ON;
|
SELECT @@global.innodb_buffer_pool_dump_at_shutdown;
|
@@global.innodb_buffer_pool_dump_at_shutdown
|
1
|
SET GLOBAL innodb_buffer_pool_dump_at_shutdown = 12.34;
|
Got one of the listed errors
|
SET GLOBAL innodb_buffer_pool_dump_at_shutdown = "string";
|
Got one of the listed errors
|
SET GLOBAL innodb_buffer_pool_dump_at_shutdown = 5;
|
Got one of the listed errors
|
At the first glance, it looks similar to MDEV-9713 / MDEV-10651, but it is not.
The test does the following:
- set innodb_buffer_pool_dump_at_shutdown = ON
- remove the dump file
- make sure it doesn't exist
- restart the server
- make sure the dump file exists now
=> and apparently it doesn't find the dump file, hence the error.
The failure has only been seen on 10.2-based branches so far.