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

Sequences of tests fail with valgrind warnings in buildbot (blocks are still reachable in loss record in malloc)

Details

    • Bug
    • Status: Closed (View Workflow)
    • Minor
    • Resolution: Fixed
    • 5.5(EOL)
    • 5.5.55
    • Tests
    • None

    Description

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

      main.udf_notembedded                     w11 [ fail ]  Found warnings/errors in server log file!
              Test ended at 2017-01-05 00:53:14
      line
      ==17254== 32 bytes in 1 blocks are still reachable in loss record 3 of 5
      ==17254==    at 0x4C28BE3: malloc (vg_replace_malloc.c:299)
      ==17254==    by 0x4014C93: _dl_close_worker (in /usr/lib64/ld-2.17.so)
      ==17254==    by 0x401529B: _dl_close (in /usr/lib64/ld-2.17.so)
      ==17254==    by 0x400F313: _dl_catch_error (in /usr/lib64/ld-2.17.so)
      ==17254==    by 0x6426DCE: __libc_dlclose (in /usr/lib64/libc-2.17.so)
      ==17254==    by 0x6459FA6: free_mem (in /usr/lib64/libc-2.17.so)
      ==17254==    by 0x6459CF1: __libc_freeres (in /usr/lib64/libc-2.17.so)
      ==17254==    by 0x4A23749: _vgnU_freeres (vg_preloaded.c:77)
      ==17254==    by 0x632F1DA: __run_exit_handlers (in /usr/lib64/libc-2.17.so)
      ==17254==    by 0x632F264: exit (in /usr/lib64/libc-2.17.so)
      ==17254==    by 0x552F8B: mysqld_exit(int) (mysqld.cc:1767)
      ==17254==    by 0x558920: mysqld_main(int, char**) (mysqld.cc:5069)
      ==17254==    by 0x5508FF: main (main.cc:25)
      ^ Found warnings in /dev/shm/var/11/log/mysqld.1.err
      

      In fact, it's a sequence of tests

      main.type_bit main.type_blob main.type_date main.type_datetime main.type_decimal main.type_enum main.type_float main.type_nchar main.type_newdecimal main.type_ranges main.type_set main.type_time main.type_timestamp main.type_uint main.type_varchar main.type_year main.udf main.udf_debug_sync main.udf_notembedded
      

      and there are more which also produce similar warnings.

      As discussed, this particular warning can be suppressed.

      Attachments

        Issue Links

          Activity

            elenst Elena Stepanova created issue -
            elenst Elena Stepanova made changes -
            Field Original Value New Value
            elenst Elena Stepanova made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            elenst Elena Stepanova made changes -
            Summary sequences of tests fail with valgrind warnings in buildbot (blocks are still reachable in loss record in malloc) Sequences of tests fail with valgrind warnings in buildbot (blocks are still reachable in loss record in malloc)
            elenst Elena Stepanova added a comment - https://github.com/MariaDB/server/commit/9e528d4fdeab83fcc75ec788da939937ce27b98d
            elenst Elena Stepanova made changes -
            Fix Version/s 5.5.55 [ 22311 ]
            Fix Version/s 5.5 [ 15800 ]
            Resolution Fixed [ 1 ]
            Status In Progress [ 3 ] Closed [ 6 ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 79105 ] MariaDB v4 [ 151491 ]

            People

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