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

main.dyncol failed in buildbot with extra warning "Warning_info flags: 0"

Details

    Description

      http://buildbot.askmonty.org/buildbot/builders/win32-debug/builds/13805

      10.3 e8dd18a4

      main.dyncol                              w3 [ fail ]  Found warnings/errors in server log file!
              Test ended at 2019-05-04 12:30:54
      line
      Warning_info  flags: 0
       
      ^ Found warnings in D:/win32-debug/build/mysql-test/var/3/log/mysqld.1.err
      ok
      

      Attachments

        Activity

          elenst Elena Stepanova created issue -

          http://buildbot.askmonty.org/buildbot/builders/winx64-debug/builds/15956/steps/test/logs/stdio

          10.4 09afd3da1a80e403b5375845770dde61832afa50

          main.dyncol                              w1 [ fail ]  Found warnings/errors in server log file!
                  Test ended at 2019-10-10 21:39:40
          line
          Warning_info  flags: 0
           
          ^ Found warnings in D:/winx64-debug/build/mysql-test/var/1/log/mysqld.1.err
          ok
          

          marko Marko Mäkelä added a comment - http://buildbot.askmonty.org/buildbot/builders/winx64-debug/builds/15956/steps/test/logs/stdio 10.4 09afd3da1a80e403b5375845770dde61832afa50 main.dyncol w1 [ fail ] Found warnings/errors in server log file! Test ended at 2019-10-10 21:39:40 line Warning_info flags: 0   ^ Found warnings in D:/winx64-debug/build/mysql-test/var/1/log/mysqld.1.err ok
          marko Marko Mäkelä made changes -
          Field Original Value New Value
          Fix Version/s 10.4 [ 22408 ]
          Affects Version/s 10.4 [ 22408 ]

          In the error log, I noticed that the preceding test main.drop_bad_db_type had inadvertently enabled all DBUG tracing by executing

          SET debug_dbug='-d,…';
          

          instead of following the preferred pattern of

          SET @save_dbug=@@debug_dbug;
          SET debug_dbug='+d,…';
          SET debug_dbug=@save_dbug;
          

          The test was introduced years ago. I searched MariaDB 5.5 for similar tests, and adjusted the main ones (notably, not --suite=rpl, because I believe that alice has been requested to do that).

          marko Marko Mäkelä added a comment - In the error log, I noticed that the preceding test main.drop_bad_db_type had inadvertently enabled all DBUG tracing by executing SET debug_dbug= '-d,…' ; instead of following the preferred pattern of SET @save_dbug=@@debug_dbug; SET debug_dbug= '+d,…' ; … SET debug_dbug=@save_dbug; The test was introduced years ago. I searched MariaDB 5.5 for similar tests, and adjusted the main ones (notably, not --suite=rpl , because I believe that alice has been requested to do that).
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 96701 ] MariaDB v4 [ 141289 ]
          julien.fritsch Julien Fritsch made changes -
          Fix Version/s 10.3 [ 22126 ]

          People

            sanja Oleksandr Byelkin
            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.