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

Galera test failure on lp1376747-4

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.3
    • 10.4.18, 10.5.9
    • Tests
    • None

    Description

      galera.lp1376747-4 'innodb'              w1 [ fail ]
              Test ended at 2020-11-14 11:36:33
       
      CURRENT_TEST: galera.lp1376747-4
      mysqltest: At line 39: query 'SHOW CREATE TABLE t1' failed: 2000: Unknown MySQL error
       
      The result from queries just before the failure was:
      < snip >
      Warning	1287	'@@wsrep_causal_reads' is deprecated and will be removed in a future release. Please use '@@wsrep_sync_wait=1' instead
      FLUSH TABLE WITH READ LOCK;
      connection node_1;
      ALTER TABLE t1 ADD COLUMN f2 INTEGER;
      INSERT INTO t1 VALUES (2,3);
      connection node_2a;
      SET session wsrep_sync_wait=0;
      SET session wsrep_causal_reads=OFF;
      Warnings:
      Warning	1287	'@@wsrep_causal_reads' is deprecated and will be removed in a future release. Please use '@@wsrep_sync_wait=1' instead
      SHOW CREATE TABLE t1;
      Table	Create Table
      t1	CREATE TABLE `t1` (
        `id` int(11) NOT NULL,
        PRIMARY KEY (`id`)
      ) ENGINE=InnoDB DEFAULT CHARSET=latin1
      FLUSH TABLES t1 WITH READ LOCK;;
      connection node_2;
      UNLOCK TABLES;
      SHOW CREATE TABLE t1;
       
      More results from queries before failure can be found in /dev/shm/var/1/log/lp1376747-4.log
      

      Attachments

        Activity

          People

            jplindst Jan Lindström (Inactive)
            jplindst Jan Lindström (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 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.