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

Port innochecksum tests from 10.2 innodb_zip suite to 10.1

Details

    Description

      Tests should be ported to innodb suite to make sure they are run.

      Attachments

        Issue Links

          Activity

            Basically port WL6045:Improve Innochecksum.

            jplindst Jan Lindström (Inactive) added a comment - Basically port WL6045:Improve Innochecksum.

            commit 2ef7a5a13a988842450cbeeaceaf0ea1a78a3c27
            Author: Jan Lindström <jan.lindstrom@mariadb.com>
            Date: Fri Aug 4 13:11:05 2017 +0300

            MDEV-13443: Port innochecksum tests from 10.2 innodb_zip suite to 10.1

            This is basically port of WL6045:Improve Innochecksum with some
            code refactoring on innochecksum.

            Added page0size.h include from 10.2 to make 10.1 vrs 10.2 innochecksum
            as identical as possible.

            Added page 0 checksum checking and if that fails whole test fails.

            jplindst Jan Lindström (Inactive) added a comment - commit 2ef7a5a13a988842450cbeeaceaf0ea1a78a3c27 Author: Jan Lindström <jan.lindstrom@mariadb.com> Date: Fri Aug 4 13:11:05 2017 +0300 MDEV-13443 : Port innochecksum tests from 10.2 innodb_zip suite to 10.1 This is basically port of WL6045:Improve Innochecksum with some code refactoring on innochecksum. Added page0size.h include from 10.2 to make 10.1 vrs 10.2 innochecksum as identical as possible. Added page 0 checksum checking and if that fails whole test fails.

            People

              jplindst Jan Lindström (Inactive)
              jplindst Jan Lindström (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.