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

Galera test failure on galera_sr_kill_slave_after_apply_rollback2

Details

    Description

      galera_3nodes_sr.galera_sr_kill_slave_after_apply_rollback2 'innodb' [ fail ]  Found warnings/errors in server log file!
              Test ended at 2022-10-27 08:49:29
      line
      safe_mutex: Trying to lock uninitialized mutex at /home/jan/mysql/10.4/sql/sql_class.cc, line 1902
      Attempting backtrace. You can use the following information to find out
      ^ Found warnings in /home/jan/mysql/10.4/mysql-test/var/log/mysqld.2.err
      

      Attachments

        Issue Links

          Activity

            janlindstrom Jan Lindström added a comment - https://github.com/MariaDB/server/pull/2948 commit c3db3fcf588

            jplindst, I do not understand the pull request; it only re-enables the test without changing any code. Because this ticket does not mention any commit hash for which the failure was observed in the first place, it could be challenging to find when the bug had been fixed.

            marko Marko Mäkelä added a comment - jplindst , I do not understand the pull request; it only re-enables the test without changing any code. Because this ticket does not mention any commit hash for which the failure was observed in the first place, it could be challenging to find when the bug had been fixed.
            sysprg Julius Goryavsky added a comment - Fix merged with head revision: https://github.com/MariaDB/server/commit/dfd2eb529a9f8bae0e02d57763d36128a0696fc2

            People

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