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

galera_sr.GCF-623: Test failure: mysqltest: Result content mismatch

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Cannot Reproduce
    • 10.4.5
    • 10.4.9
    • Galera
    • OS: CentOS Linux release 7.6.1810 (Core).

    Description

      MariaDB Server: 10.4.5-MariaDB-debug built from sources, branch=10.4, commit: e4c5551964f398ebbe2b1b34fef028eff6f22fbe.
      Galera4 lib: debug built from sources, commit: a4890d84092bfeb279f1c0c0feb73e4d9c383220.

      Run: 

      ./mtr --suite galera_sr --force --big-test --max-test-fail=0 --parallel=auto --timer --timestamp --timediff

      stdout.log: (the whole file is attached: 190415_galera_sr_stdout_SSD.log)

      190415 21:35:05 +1.587 galera_sr.GCF-623 'innodb'               w2 [ fail ]
      		 
       
      		 
      @@ -25,5 +25,5 @@
      		 
       connection node_2;
      		 
       SELECT COUNT(*) = 0 FROM mysql.wsrep_streaming_log;
      		 
       COUNT(*) = 0
      		 
      -1
      		 
      +0
      		 
       DROP TABLE t1;
      		 
       
      		 
      mysqltest: Result content mismatch

      See also attached 190415_galera_sr.GCF-623-innodb.zip.

      Note: This test is failed sporadically.

      Attachments

        Issue Links

          relates to

          Task - A task that needs to be done. MDEV-17046 Galera 4: Streaming replication

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              stepan.patryshev Stepan Patryshev (Inactive)
              stepan.patryshev Stepan Patryshev (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 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.