Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
10.1(EOL)
-
None
Description
http://buildbot.askmonty.org/buildbot/builders/winx64-debug/builds/1089/steps/test/logs/stdio
innodb.innodb_stats_fetch_nonexistent 'innodb_plugin' w2 [ fail ] Found warnings/errors in server log file!
|
Test ended at 2016-09-24 12:25:49
|
line
|
2016-09-24 12:25:47 cd8 InnoDB: Error: Table "mysql"."innodb_index_stats" not found.
|
|
The test fails since commit 2bedc3978b90bf5abe1029df393c63ced1849bed
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | In Progress [ 3 ] |
commit 661d08c36ca9181e9f2469c66160e877e284c23f
Author: Jan Lindström <jan.lindstrom@mariadb.com>
Date: Mon Sep 26 15:16:00 2016 +0300
MDEV-10887: innodb.innodb_stats_fetch_nonexistent fails in buildbot on Windows
Problem was that test innodb.innodb_stats_fetch_corrupted will post
a error InnoDB: Error: Table "mysql"."innodb_index_stats" not found
to a error log and test ignores that message. However, following tests
might see this error also and they might not ignore this error.
Force a server restart after innodb.innodb_stats_fetch_corrupted
to get clean log.
| issue.field.resolutiondate | 2016-09-27 05:01:19.0 | 2016-09-27 05:01:19.354 |
| Component/s | Storage Engine - InnoDB [ 10129 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
| Workflow | MariaDB v3 [ 77217 ] | MariaDB v4 [ 150961 ] |
Repeatable with:
mysql-test-run.pl innodb.innodb_stats_fetch_corrupted,innodb_plugin innodb.innodb_stats_fetch_nonexistent,innodb_plugin