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

Galera test failure on GCF-360

    XMLWordPrintable

Details

    • Not for Release Notes
    • Q3/2026 Replic. Maintenance

    Description

      https://es-jenkins.mariadb.net/job/Test-Package//740257/artifact/test-MTR-custom.log/*view*

      galera.GCF-360                           w4 [ fail ]
              Test ended at 2026-05-29 02:13:12
       
      CURRENT_TEST: galera.GCF-360
      --- /home/jenkins/workspace/Test-Package/mariadb-test/suite/galera/r/GCF-360.result	2026-05-29 01:51:28.000000000 +0000
      +++ /home/jenkins/workspace/Test-Package/mariadb-test/suite/galera/r/GCF-360.reject	2026-05-29 02:13:02.611066799 +0000
      @@ -2,6 +2,7 @@
       connection node_1;
       connect node_3, 127.0.0.1, root, , test, $NODE_MYPORT_3;
       connect node_4, 127.0.0.1, root, , test, $NODE_MYPORT_4;
      +mysqltest: At line 47: query 'reap' failed with wrong errno ER_QUERY_INTERRUPTED (1317): 'Query execution was interrupted', instead of ER_BAD_TABLE_ERROR (1051)...
       connection node_1;
       SELECT VARIABLE_VALUE AS expect_4 FROM INFORMATION_SCHEMA.GLOBAL_STATUS WHERE VARIABLE_NAME = 'wsrep_cluster_size';
       expect_4
       
      Result length mismatch
      

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - 0.5d
                0.5d
                Remaining:
                Remaining Estimate - 0d
                0d
                Logged:
                Time Spent - 2.5h Time Not Required
                2.5h

                Git Integration

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