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

main.default_debug fails with view-protocol in a chain of tests

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.4(EOL), 10.5, 10.6, 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL), 11.2(EOL)
    • 10.5, 10.6, 10.11
    • Tests
    • None

    Description

      10.4 9e321a44

      		 
      $ perl ./mtr --noreorder --mem main.sp_notembedded main.default_debug --view-protocol
      		 
       
      		 
      ...
      		 
      main.sp_notembedded                      [ skipped ]  Test requires: view-protocol disabled
      		 
      main.default_debug                       [ fail ]
      		 
              Test ended at 2023-11-09 00:44:29
      		 
       
      		 
      CURRENT_TEST: main.default_debug
      		 
      --- /mnt8t/bld/10.4-asan/mysql-test/main/default_debug.result	2023-03-23 01:27:25.000000000 +0200
      		 
      +++ /mnt8t/bld/10.4-asan/mysql-test/main/default_debug.reject	2023-11-09 00:44:29.241886091 +0200
      		 
      @@ -16,6 +16,8 @@
      		 
       1	10	2
      		 
       2	20	3
      		 
       3	30	4
      		 
      +Warnings:
      		 
      +Warning	1639	debug sync point wait timed out
      		 
       connection default;
      		 
       drop table t1;
      		 
       set debug_sync='RESET';
      		 
       
      		 
      mysqltest: Result length mismatch

      Attachments

        Activity

          lstartseva Lena Startseva added a comment - - edited

          This problem is not only view-protocol's problem.The problem repeats for all protocols if first test contains condition like this:

          if (`SELECT $PS_PROTOCOL + $SP_PROTOCOL + $CURSOR_PROTOCOL
          		 
                      + $VIEW_PROTOCOL > 0`)
          		 
          {
          		 
             --skip Test requires: ps-protocol/sp-protocol/cursor-protocol/view-protocol disabled
          		 
          }

          The bug consists in that the first test changes the value of the variable concurrent_insert to 0 (set @@global.concurrent_insert= 0; ), and only then the test was excluded from the run. So the value of variable was not reset

          lstartseva Lena Startseva added a comment - - edited This problem is not only view-protocol's problem.The problem repeats for all protocols if first test contains condition like this: if (` SELECT $PS_PROTOCOL + $SP_PROTOCOL + $CURSOR_PROTOCOL + $VIEW_PROTOCOL > 0`) { --skip Test requires: ps-protocol/sp-protocol/cursor-protocol/view-protocol disabled } The bug consists in that the first test changes the value of the variable concurrent_insert to 0 (set @@global.concurrent_insert= 0; ), and only then the test was excluded from the run. So the value of variable was not reset

          People

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