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

Warnings "bytes lost" during server shutdown after running connect.part_file test in buildbot

    XMLWordPrintable

Details

    Description

      Buildbot example: http://buildbot.askmonty.org/buildbot/builders/kvm-dgcov-jaunty-i386/builds/4449/steps/test_2/logs/stdio

      I can reproduce the problem by running the test with valgrind on a debug build. The valgrind report goes OK, but the warnings are generated on shutdown. It happens almost every time when I run the test:

      perl ./mtr connect.part_file  --valgrind-mysqld
      Logging: ./mtr  connect.part_file --valgrind-mysqld
      ...
       
      worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 16000..16019
      connect.part_file                        [ pass ]   4482
      ***Warnings generated in error logs during shutdown after running tests: connect.part_file
       
      Warning: 65536 bytes lost at 0xfaea070, allocated by T@0 at 
      valgrind_report                          [ pass ]       
      --------------------------------------------------------------------------
      The servers were restarted 0 times
      Spent 4.482 of 31 seconds executing testcases
       
      Warnings in log: All 2 tests were successful.
       
      Errors/warnings were found in logfiles during server shutdown after running the
      following sequence(s) of tests:
          connect.part_file
      mysql-test-run: *** ERROR: There where errors/warnings in server logs after running test cases.

      Attachments

        Issue Links

          Activity

            People

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