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

main.multi_update_debug failed in buildbot with debug sync point wait timed out

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • 10.1(EOL), 10.3(EOL), 10.4(EOL)
    • 10.2.32
    • Tests
    • None

    Description

      http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/14916/steps/test/logs/stdio

      10.1 10ebdb7f1d7a3f6aa6a91b40a9d90f48

      		 
      main.multi_update_debug                  w1 [ fail ]
      		 
              Test ended at 2019-07-15 08:39:48
      		 
       
      		 
      CURRENT_TEST: main.multi_update_debug
      		 
      --- D:/win32-debug/build/src/mysql-test/r/multi_update_debug.result	2019-07-15 08:07:05.143117000 +0000
      		 
      +++ D:\win32-debug\build\src\mysql-test\r\multi_update_debug.reject	2019-07-15 08:39:47.822875200 +0000
      		 
      @@ -9,5 +9,7 @@
      		 
       update t1 join t2 on (a=c+4) set b=d;
      		 
       set debug_sync='mdl_acquire_lock_wait SIGNAL cont';
      		 
       lock table t1 write, t0 write;
      		 
      +Warnings:
      		 
      +Warning	1639	debug sync point wait timed out
      		 
       drop table t1, t2, t0;
      		 
       set debug_sync='reset';
      		 
       
      		 
      mysqltest: Result length mismatch

      http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/18387

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-19491 update query stopped working after mariadb upgrade 10.2.23 -> 10.2.24

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            midenok Aleksey Midenkov added a comment -

            Unstable in bb-10.3-midenok which is based on relatively late 10.3 (e555df648c5c81f):

            --- /mnt/buildbot/build/mariadb-10.3.18/mysql-test/main/multi_update_debug.result	2019-08-09 10:01:20.000000000 -0400
            		 
            +++ /mnt/buildbot/build/mariadb-10.3.18/mysql-test/main/multi_update_debug.reject	2019-08-09 13:52:23.774742025 -0400
            		 
            @@ -12,5 +12,7 @@
            		 
             lock table t1 write, t0 write;
            		 
             disconnect con1;
            		 
             connection default;
            		 
            +Warnings:
            		 
            +Warning	1639	debug sync point wait timed out
            		 
             drop table t1, t2, t0;
            		 
             set debug_sync='reset';

            midenok Aleksey Midenkov added a comment - Unstable in bb-10.3-midenok which is based on relatively late 10.3 (e555df648c5c81f): --- /mnt/buildbot/build/mariadb-10.3.18/mysql-test/main/multi_update_debug.result 2019-08-09 10:01:20.000000000 -0400 +++ /mnt/buildbot/build/mariadb-10.3.18/mysql-test/main/multi_update_debug.reject 2019-08-09 13:52:23.774742025 -0400 @@ -12,5 +12,7 @@ lock table t1 write, t0 write; disconnect con1; connection default; +Warnings: +Warning 1639 debug sync point wait timed out drop table t1, t2, t0; set debug_sync='reset';
            midenok Aleksey Midenkov added a comment -

            Not found this issue in 10.3 kvm-fulltest2 (grid width 32) though.

            midenok Aleksey Midenkov added a comment - Not found this issue in 10.3 kvm-fulltest2 (grid width 32) though.
            marko Marko Mäkelä added a comment -

            This has been failing for me locally for various branches, every now and then. The latest occurrence was on 10.4 today:

            10.4 efb8485d85b19a2a729310adc6779ca649198f29

            		 
            CURRENT_TEST: main.multi_update_debug
            		 
            --- /mariadb/10.4/mysql-test/main/multi_update_debug.result	2019-08-12 13:50:58.608699851 +0300
            		 
            +++ /mariadb/10.4/mysql-test/main/multi_update_debug.reject	2019-08-23 08:15:25.171705567 +0300
            		 
            @@ -12,5 +12,7 @@
            		 
             lock table t1 write, t0 write;
            		 
             disconnect con1;
            		 
             connection default;
            		 
            +Warnings:
            		 
            +Warning	1639	debug sync point wait timed out
            		 
             drop table t1, t2, t0;
            		 
             set debug_sync='reset';
            		 
             
            		 
            mysqltest: Result length mismatch

            marko Marko Mäkelä added a comment - This has been failing for me locally for various branches, every now and then. The latest occurrence was on 10.4 today: 10.4 efb8485d85b19a2a729310adc6779ca649198f29 CURRENT_TEST: main.multi_update_debug --- /mariadb/10.4/mysql-test/main/multi_update_debug.result 2019-08-12 13:50:58.608699851 +0300 +++ /mariadb/10.4/mysql-test/main/multi_update_debug.reject 2019-08-23 08:15:25.171705567 +0300 @@ -12,5 +12,7 @@ lock table t1 write, t0 write; disconnect con1; connection default; +Warnings: +Warning 1639 debug sync point wait timed out drop table t1, t2, t0; set debug_sync='reset';   mysqltest: Result length mismatch
            monty Michael Widenius added a comment -

            I got this on latest 10.4 code today

            monty Michael Widenius added a comment - I got this on latest 10.4 code today
            monty Michael Widenius added a comment -

            Already fixed in 10.5 by svoj. Backported to 10.2

            monty Michael Widenius added a comment - Already fixed in 10.5 by svoj. Backported to 10.2

            People

              svoj Sergey Vojtovich
              elenst Elena Stepanova
              Votes:
              1 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.