Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Fixed
-
10.0(EOL), 10.1(EOL)
-
None
-
10.1.29
Description
sys_vars.innodb_buffer_pool_dump_pct_basic 'xtradb' w2 [ fail ]
|
Test ended at 2016-08-23 23:43:20
|
|
CURRENT_TEST: sys_vars.innodb_buffer_pool_dump_pct_basic
|
mysqltest: At line 23: command "file_exists" failed with error: 1 my_errno: 0 errno: 2
|
|
The result from queries just before the failure was:
|
SET @orig = @@global.innodb_buffer_pool_dump_pct;
|
SELECT @orig;
|
@orig
|
100
|
SET GLOBAL innodb_buffer_pool_dump_pct=3, GLOBAL innodb_buffer_pool_dump_now = ON;
|
By now there have been 5 recorded occurrences - on 10.0, 10.2, and 3 times on bb-10.1-serg.
Running the same sequence of tests does not cause the failure. There might be a race condition similar to the one recently fixed in another buffer_pool test.
Attachments
Issue Links
- relates to
-
MDEV-9713 Sporadic test failure: sys_vars.innodb_buffer_pool_load_now_basic
-
- Closed
-
-
MDEV-14196 sys_vars.innodb_buffer_pool_load_now_basic failed in buildbot with timeout
-
- Closed
-
-
MDEV-7069 Fix buildbot failures in main server trees
-
- Closed
-
Okay, so, the patch was only pushed in 10.2. Saving the default value is redundant (because the test sets it at the end to Default anyway), but innocent, so let it be. unstable-tests list in 10.2 is meaningless, it shouldn't even be there, just got merged along with everything else. When the time comes, it will be created from scratch, it doesn't matter what's there now, so I won't roll back the change.
The real problem is that the fix has nothing to do with the bug, I wish the commit message didn't mention this JIRA item. The problem for 10.0 and 10.1 remains (and no, we can't just disable the test as long as the variable exists). I'll keep the bug open, even though it will create a mess in the history, hopefully it won't matter much since it's just a test.
Please in future create a different JIRA item.