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

galera tests failing with Table performance_schema.xxx doesn't exist

    XMLWordPrintable

Details

    • Bug
    • Status: In Review (View Workflow)
    • Minor
    • Resolution: Unresolved
    • N/A
    • N/A
    • Galera

    Description

      The testcase galera.galera_ssl_upgrade galera_3nodes.galera_vote_majority_dml galera.galera_multi_level_fk_ddl_delete galera.galera_multi_level_fk_ddl_update galera.galera_multi_level_fk_ddl_insert fails when mariadb 10.11 build without performance_schema plugin is run.

      cmake -DPLUGIN_PERFSCHEMA=NO
      

      fails

      ./mtr  --big-test --force galera.galera_sst_mariabackup_use_memory galera.galera_ssl_upgrade galera.galera_multi_level_fk_ddl_delete galera.galera_multi_level_fk_ddl_insert galera_3nodes.galera_vote_majority_dml galera.galera_multi_level_fk_ddl_update
      ...
      galera.galera_ssl_upgrade                w6 [ fail ]
              Test ended at 2025-10-07 18:59:47
       
      CURRENT_TEST: galera.galera_ssl_upgrade
      mysqltest: At line 14: query 'SELECT COUNT(*) `expect 0` FROM performance_schema.socket_instances WHERE EVENT_NAME LIKE '%wsrep%'' failed: ER_NO_SUCH_TABLE (1146): Table 'performance_schema.socket_instances' doesn't exist
      ...
      ...
      Completed: Failed 5/6 tests, 16.67% were successful.
       
      Failing test(s): galera.galera_ssl_upgrade galera_3nodes.galera_vote_majority_dml galera.galera_multi_level_fk_ddl_delete galera.galera_multi_level_fk_ddl_update galera.galera_multi_level_fk_ddl_insert
      

      Attachments

        Activity

          People

            janlindstrom Jan Lindström
            hemantdangi Hemant Dangi
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

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