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

perfschema.stage_mdl_global fails in buildbot on very slow builders

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.1(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL)
    • 10.5, 10.6
    • Performance Schema, Tests

    Description

      http://buildbot.askmonty.org/buildbot/builders/xenial-amd64-valgrind/builds/296/steps/test/logs/stdio

      perfschema.stage_mdl_global              w19 [ fail ]
              Test ended at 2017-01-12 14:42:22
       
      CURRENT_TEST: perfschema.stage_mdl_global
      --- /home/buildbot/build/mysql-test/suite/perfschema/r/stage_mdl_global.result	2017-01-12 07:57:26.000000000 -0500
      +++ /home/buildbot/build/mysql-test/suite/perfschema/r/stage_mdl_global.reject	2017-01-12 14:42:21.804961532 -0500
      @@ -22,4 +22,6 @@
       user2	stage/sql/init	STATEMENT
       user2	stage/sql/checking permissions	STATEMENT
       user2	stage/sql/Opening tables	STATEMENT
      +user2	stage/sql/Waiting for global read lock	STATEMENT
      +user2	stage/sql/Opening tables	STATEMENT
       unlock tables;
       
      mysqltest: Result length mismatch
      

      Attachments

        Issue Links

          Activity

            amd64-windows is not a very slow builder (it is extremely fast), and the test failed there:

            10.6 7d92c9d212162287b52721fcea1217115853b4f7

            perfschema.stage_mdl_global              w30 [ fail ]
                    Test ended at 2022-06-27 10:12:01
            CURRENT_TEST: perfschema.stage_mdl_global
            --- D:/Buildbot/amd64-windows/build/mysql-test/suite/perfschema/r/stage_mdl_global.result	2022-06-27 10:07:23.000000000 +0200
            +++ D:\Buildbot\amd64-windows\build\mysql-test\suite\perfschema\r\stage_mdl_global.reject	2022-06-27 10:12:01.545503700 +0200
            @@ -23,8 +23,15 @@
             username	event_name	nesting_event_type
             user2	stage/sql/Waiting for backup lock	STATEMENT
             username	event_name	nesting_event_type
            -user2	stage/sql/starting	STATEMENT
            -user2	stage/sql/checking permissions	STATEMENT
            +user2	stage/sql/Waiting for backup lock	STATEMENT
            +user2	stage/sql/Opening tables	STATEMENT
            +user2	stage/sql/Waiting for backup lock	STATEMENT
            +user2	stage/sql/Opening tables	STATEMENT
            +user2	stage/sql/Waiting for backup lock	STATEMENT
            +user2	stage/sql/Opening tables	STATEMENT
            +user2	stage/sql/Waiting for backup lock	STATEMENT
            +user2	stage/sql/Opening tables	STATEMENT
            +user2	stage/sql/Waiting for backup lock	STATEMENT
             user2	stage/sql/Opening tables	STATEMENT
             connection con1;
             unlock tables;
            mysqltest: Result length mismatch
            

            Because this test failed as part of mandatory staging build, I think that we should do something about it. The failure output suggests that MDEV-5336 (backup locks) could be related to it.

            marko Marko Mäkelä added a comment - amd64-windows is not a very slow builder (it is extremely fast), and the test failed there : 10.6 7d92c9d212162287b52721fcea1217115853b4f7 perfschema.stage_mdl_global w30 [ fail ] Test ended at 2022-06-27 10:12:01 CURRENT_TEST: perfschema.stage_mdl_global --- D:/Buildbot/amd64-windows/build/mysql-test/suite/perfschema/r/stage_mdl_global.result 2022-06-27 10:07:23.000000000 +0200 +++ D:\Buildbot\amd64-windows\build\mysql-test\suite\perfschema\r\stage_mdl_global.reject 2022-06-27 10:12:01.545503700 +0200 @@ -23,8 +23,15 @@ username event_name nesting_event_type user2 stage/sql/Waiting for backup lock STATEMENT username event_name nesting_event_type -user2 stage/sql/starting STATEMENT -user2 stage/sql/checking permissions STATEMENT +user2 stage/sql/Waiting for backup lock STATEMENT +user2 stage/sql/Opening tables STATEMENT +user2 stage/sql/Waiting for backup lock STATEMENT +user2 stage/sql/Opening tables STATEMENT +user2 stage/sql/Waiting for backup lock STATEMENT +user2 stage/sql/Opening tables STATEMENT +user2 stage/sql/Waiting for backup lock STATEMENT +user2 stage/sql/Opening tables STATEMENT +user2 stage/sql/Waiting for backup lock STATEMENT user2 stage/sql/Opening tables STATEMENT connection con1; unlock tables; mysqltest: Result length mismatch Because this test failed as part of mandatory staging build, I think that we should do something about it. The failure output suggests that MDEV-5336 (backup locks) could be related to it.

            People

              serg Sergei Golubchik
              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.