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

mariabackup.unencrypted_page_compressed failed in buildbot with wrong error

Details

    Description

      http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/12063

      mariabackup.unencrypted_page_compressed  w3 [ fail ]
              Test ended at 2019-01-14 08:38:28
       
      CURRENT_TEST: mariabackup.unencrypted_page_compressed
      mysqltest: At line 41: command "$XTRABACKUP --defaults-file=$MYSQLTEST_VARDIR/my.cnf --backup --target-dir=$targetdir > $backuplog" failed with wrong error: 255
       
      The result from queries just before the failure was:
      call mtr.add_suppression("InnoDB: Table `test`.`t1` has an unreadable root page");
      SET GLOBAL innodb_purge_rseg_truncate_frequency = 1;
      CREATE TABLE t1 (a INT AUTO_INCREMENT PRIMARY KEY, b TEXT, c char(200)) ENGINE=InnoDB page_compressed=yes;
      insert into t1(b, c) values("mariadb", "mariabackup");
      InnoDB		0 transactions not purged
      # Corrupt the table
      # xtrabackup backup
      

      Attachments

        Issue Links

          Activity

            Exit code 255 on Windows is a sign of crash. It would typically correspond to 134 (128 + SIGABRT) or 139 (128 + SIGSEGV) on Linux.

            This is a test for MDEV-18025. It revealed wrong usage of a zlib function, which would cause failures depending on zlib version, and was subsequently fixed by me as a follow-up commit to MDEV-18025.

            Unfortunately, we do not save the output of failed the command anywhere, and it seems nontrivial to modify the test to output the log in case of befailure.

            An educated guess is that this failure might be a duplicate of MDEV-14192, which occurs every now and then on mariabackup tests.

            marko Marko Mäkelä added a comment - Exit code 255 on Windows is a sign of crash. It would typically correspond to 134 (128 + SIGABRT) or 139 (128 + SIGSEGV) on Linux. This is a test for MDEV-18025 . It revealed wrong usage of a zlib function, which would cause failures depending on zlib version, and was subsequently fixed by me as a follow-up commit to MDEV-18025 . Unfortunately, we do not save the output of failed the command anywhere, and it seems nontrivial to modify the test to output the log in case of befailure. An educated guess is that this failure might be a duplicate of MDEV-14192 , which occurs every now and then on mariabackup tests.

            Could be related to MDEV-14192. So assigning to vlad.lesin

            thiru Thirunarayanan Balathandayuthapani added a comment - Could be related to MDEV-14192 . So assigning to vlad.lesin

            People

              marko Marko Mäkelä
              elenst Elena Stepanova
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.