Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.4(EOL)
-
None
Description
http://buildbot.askmonty.org/buildbot/builders/winx64-debug/builds/14481/steps/test/logs/stdio
10.4 9c16460e63a5002d5949f67f57dce71e |
main.mysql_upgrade_view w2 [ fail ]
|
Test ended at 2019-07-01 20:46:42
|
|
CURRENT_TEST: main.mysql_upgrade_view
|
--- D:/winx64-debug/build/src/mysql-test/main/mysql_upgrade_view.result 2019-07-01 20:04:59.046078700 +0000
|
+++ D:\winx64-debug\build\src\mysql-test\main\mysql_upgrade_view.reject 2019-07-01 20:46:41.853309200 +0000
|
@@ -338,54 +338,6 @@
|
The --upgrade-system-tables option was used, user tables won't be touched.
|
MariaDB upgrade detected
|
Phase 1/7: Checking and upgrading mysql database
|
-Processing databases
|
-mysql
|
-mysql.column_stats OK
|
-mysql.columns_priv OK
|
-mysql.db OK
|
-mysql.ev_bk OK
|
-mysql.event OK
|
-mysql.func OK
|
-mysql.global_priv OK
|
-mysql.gtid_slave_pos OK
|
-mysql.help_category OK
|
-mysql.help_keyword OK
|
-mysql.help_relation OK
|
-mysql.help_topic OK
|
-mysql.index_stats OK
|
-mysql.innodb_index_stats
|
-Error : Unknown storage engine 'InnoDB'
|
-error : Corrupt
|
-mysql.innodb_table_stats
|
-Error : Unknown storage engine 'InnoDB'
|
-error : Corrupt
|
-mysql.plugin OK
|
-mysql.proc OK
|
-mysql.procs_priv OK
|
-mysql.proxies_priv OK
|
-mysql.roles_mapping OK
|
-mysql.servers OK
|
-mysql.table_stats OK
|
-mysql.tables_priv OK
|
-mysql.time_zone OK
|
-mysql.time_zone_leap_second OK
|
-mysql.time_zone_name OK
|
-mysql.time_zone_transition OK
|
-mysql.time_zone_transition_type OK
|
-mysql.transaction_registry
|
-Error : Unknown storage engine 'InnoDB'
|
-error : Corrupt
|
-
|
-Repairing tables
|
-mysql.innodb_index_stats
|
-Error : Unknown storage engine 'InnoDB'
|
-error : Corrupt
|
-mysql.innodb_table_stats
|
-Error : Unknown storage engine 'InnoDB'
|
-error : Corrupt
|
-mysql.transaction_registry
|
-Error : Unknown storage engine 'InnoDB'
|
-error : Corrupt
|
Phase 2/7: Installing used storage engines... Skipped
|
Phase 3/7: Fixing views from mysql
|
mysql.user OK
|
|
mysqltest: Result length mismatch
|
Somewhat similar failure with main.mysql_upgrade:
http://buildbot.askmonty.org/buildbot/builders/win32-packages/builds/13997/steps/test/logs/stdio
10.4 b7b0bc8f11c7cbbc690fa9b704ab3b0f |
main.mysql_upgrade 'innodb' w1 [ fail ]
|
Test ended at 2019-06-28 01:22:03
|
|
CURRENT_TEST: main.mysql_upgrade
|
--- D:/win32-packages/build/src/mysql-test/main/mysql_upgrade.result 2019-06-27 15:03:33.000000000 +0000
|
+++ D:\win32-packages\build\src\mysql-test\main\mysql_upgrade.reject 2019-06-28 01:22:02.779666300 +0000
|
@@ -465,13 +465,6 @@
|
Phase 4/7: Running 'mysql_fix_privilege_tables'
|
Phase 5/7: Fixing table and database names
|
Phase 6/7: Checking and upgrading tables
|
-Processing databases
|
-information_schema
|
-mtr
|
-mtr.global_suppressions OK
|
-mtr.test_suppressions OK
|
-performance_schema
|
-test
|
Phase 7/7: Running 'FLUSH PRIVILEGES'
|
OK
|
SELECT definer FROM mysql.proc WHERE db = 'test' AND name = 'pr';
|
|
mysqltest: Result length mismatch
|
Attachments
Issue Links
- relates to
-
MDEV-20164 main.mysqlcheck failed in buildbot with wrong result
- Open
-
MDEV-23392 main.mysql_upgrade_view failed in buildbot with another wrong result
- Closed