[MDEV-10887] innodb.innodb_stats_fetch_nonexistent fails in buildbot on Windows Created: 2016-09-25  Updated: 2016-09-27  Resolved: 2016-09-27

Status: Closed
Project: MariaDB Server
Component/s: Platform Windows, Tests
Affects Version/s: 10.1
Fix Version/s: 10.1.18

Type: Bug Priority: Blocker
Reporter: Elena Stepanova Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 0
Labels: 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

 Comments   
Comment by Jan Lindström (Inactive) [ 2016-09-26 ]

Repeatable with:

mysql-test-run.pl innodb.innodb_stats_fetch_corrupted,innodb_plugin innodb.innodb_stats_fetch_nonexistent,innodb_plugin

Comment by Jan Lindström (Inactive) [ 2016-09-27 ]

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.

Generated at Thu Feb 08 07:45:41 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.