Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-14235

main.mysql_upgrade_noengine failed, results mismatch

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.3(EOL)
    • 10.3.3
    • Tests
    • None
    • win64

    Description

      http://buildbot.askmonty.org/buildbot/builders/winx64-packages/builds/5516/steps/test/logs/stdio

      main.mysql_upgrade_noengine 'innodb'     w2 [ retry-fail ]
              Test ended at 2017-10-31 16:50:23
       
      CURRENT_TEST: main.mysql_upgrade_noengine
      --- D:/winx64-packages/build/src/mysql-test/r/mysql_upgrade_noengine.result	2017-10-31 15:17:24.000000000 +0000
      +++ D:\winx64-packages\build\src\mysql-test\r\mysql_upgrade_noengine.reject	2017-10-31 16:50:23.751918000 +0000
      @@ -263,8 +263,8 @@
       Upgrading from a version before MariaDB-10.1
       Phase 2/7: Installing used storage engines
       Checking for tables with unknown storage engine
      -installing plugin for 'archive' storage engine
       installing plugin for 'blackhole' storage engine
      +installing plugin for 'archive' storage engine
       Phase 3/7: Fixing views
       Phase 4/7: Running 'mysql_fix_privilege_tables'
       Phase 5/7: Fixing table and database names
       
      mysqltest: Result content mismatch
      

      Attachments

        Activity

          another one of I_S sorting artifacts?

          serg Sergei Golubchik added a comment - another one of I_S sorting artifacts?

          Yes, looks like this.

          bar Alexander Barkov added a comment - Yes, looks like this.
          alice Alice Sherepa added a comment -

          http://buildbot.askmonty.org/buildbot/builders/p8-rhel6-bintar-debug/builds/1404/steps/test/logs/stdio

          main.mysql_upgrade_noengine 'innodb_plugin' w3 [ fail ]
                  Test ended at 2017-11-03 18:58:03
           
          CURRENT_TEST: main.mysql_upgrade_noengine
          --- /home/buildbot/maria-slave/p8-rhel6-bintar-debug/build/mysql-test/r/mysql_upgrade_noengine.result	2017-11-03 16:29:33.750049495 -0400
          +++ /home/buildbot/maria-slave/p8-rhel6-bintar-debug/build/mysql-test/r/mysql_upgrade_noengine.reject	2017-11-03 18:58:02.870049493 -0400
          @@ -294,4 +294,12 @@
           table_comment	
           drop table t1, t2;
           uninstall plugin blackhole;
          +Warnings:
          +Level	Warning
          +Code	1620
          +Message	Plugin is busy and will be uninstalled on shutdown
           uninstall plugin archive;
          +Warnings:
          +Level	Warning
          +Code	1620
          +Message	Plugin is busy and will be uninstalled on shutdown
           
          mysqltest: Result length mismatch
          

          alice Alice Sherepa added a comment - http://buildbot.askmonty.org/buildbot/builders/p8-rhel6-bintar-debug/builds/1404/steps/test/logs/stdio main.mysql_upgrade_noengine 'innodb_plugin' w3 [ fail ] Test ended at 2017-11-03 18:58:03   CURRENT_TEST: main.mysql_upgrade_noengine --- /home/buildbot/maria-slave/p8-rhel6-bintar-debug/build/mysql-test/r/mysql_upgrade_noengine.result 2017-11-03 16:29:33.750049495 -0400 +++ /home/buildbot/maria-slave/p8-rhel6-bintar-debug/build/mysql-test/r/mysql_upgrade_noengine.reject 2017-11-03 18:58:02.870049493 -0400 @@ -294,4 +294,12 @@ table_comment drop table t1, t2; uninstall plugin blackhole; +Warnings: +Level Warning +Code 1620 +Message Plugin is busy and will be uninstalled on shutdown uninstall plugin archive; +Warnings: +Level Warning +Code 1620 +Message Plugin is busy and will be uninstalled on shutdown   mysqltest: Result length mismatch

          People

            bar Alexander Barkov
            alice Alice Sherepa
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.