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

innodb.innodb_sys_semaphore_waits fails with wrong errno 5014

    XMLWordPrintable

Details

    Description

      10.5 a3fd9e6b064e28256f932595fb5f2ac3c33072fc

      innodb.innodb_sys_semaphore_waits 'innodb' w4 [ fail ]
              Test ended at 2022-08-24 12:29:31
       
      CURRENT_TEST: innodb.innodb_sys_semaphore_waits
      mysqltest: At line 94: query 'show status' failed with wrong errno 5014: 'Write error: Broken pipe (32)', instead of 0...
       
      The result from queries just before the failure was:
      < snip >
      connection con1;
      create table t1 (id integer, x integer) engine = InnoDB;
      insert into t1 values(0, 0);
      SET @saved_dbug = @@SESSION.debug_dbug;
      set DEBUG_DBUG='+d,fatal-semaphore-timeout';
      set autocommit=0;
      # Sending query on con1,
      # the session will hold lock table mutex and sleep
      SELECT * from t1 where id = 0 FOR UPDATE;
      connection con2;
      set autocommit=0;
      # Sending query on con2,
      # the session will be blocked on the lock table mutex and
      # thus be put into sync arry
      SELECT * from t1 where id = 0 FOR UPDATE;
      connection default;
      # Waitting for mysqld to crash
      

      Needs the same fix as innodb_fatal_semaphore_wait_threshold.test
      https://github.com/MariaDB/server/commit/47d0df6ef02fa1acd5581d1322475a08be3066f5

      -  --error 0,ER_SERVER_SHUTDOWN,ER_CONNECTION_KILLED,2002,2006,2013
      +  --error 0,ER_SERVER_SHUTDOWN,ER_CONNECTION_KILLED,2002,2006,2013,5014
      

      Attachments

        Activity

          People

            elenst Elena Stepanova
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            1 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.