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

Tests fail massively on "Assertion `status_var.memory_used == 0'" when run with --ps --embedded

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 10.0, 10.1
    • Fix Version/s: 10.0.21
    • Component/s: Tests
    • Labels:
      None
    • Sprint:
      10.0.20

      Description

      fulltest2/test_9 hits the limit of failed tests.
      http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/3583/steps/test_9/logs/stdio

      If I just run the sys_vars suite with --ps --embedded, it fails badly.

      sys_vars.version_compile_os_basic        [ fail ]
              Test ended at 2015-03-29 19:16:55
       
      CURRENT_TEST: sys_vars.version_compile_os_basic
      Warning: 4120 bytes lost at 0x41664a0, allocated by T@1 at mysys/my_alloc.c:74, libmysql/libmysql.c:1531, client/mysqltest.cc:8152, client/mysqltest.cc:8594, client/mysqltest.cc:9
      378, 0x7f2d6da12ead, 0x5a72f9
      Warning: 2072 bytes lost at 0x4165c00, allocated by T@1 at mysys/my_alloc.c:74, libmysql/libmysql.c:1530, client/mysqltest.cc:8152, client/mysqltest.cc:8594, client/mysqltest.cc:9
      378, 0x7f2d6da12ead, 0x5a72f9
      Memory lost: 6192 bytes in 569 chunks
      mysqltest_embedded: /home/elenst/git/10.0/sql/sql_class.cc:1633: virtual THD::~THD(): Assertion `status_var.memory_used == 0' failed.
      mysqltest got signal 6
      read_command_buf (0x17b38a0): 
      conn->name (0x4151e70): 
      conn->cur_query (0x4185c60): SELECT version_compile_os = @@SESSION.version_compile_os
      Attempting backtrace...
      stack_bottom = 0x0 thread_stack 0x48000
      mysys/stacktrace.c:246(my_print_stacktrace)[0x5dde1e]
      client/mysqltest.cc:8870(dump_backtrace)[0x5b7fc0]
      client/mysqltest.cc:8886(signal_handler)[0x5b7ff3]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0)[0x7f2d6f5e20a0]
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7f2d6da26165]
      /lib/x86_64-linux-gnu/libc.so.6(abort+0x180)[0x7f2d6da293e0]
      /lib/x86_64-linux-gnu/libc.so.6(__assert_fail+0xf1)[0x7f2d6da1f311]
      sql/sql_class.cc:1636(THD::~THD())[0x676bc7]
      sql/sql_class.cc:1638(THD::~THD())[0x676d4a]
      libmysqld/lib_sql.cc:440(emb_free_embedded_thd)[0x61739a]
      sql-common/client.c:4096(mysql_close)[0x5eee97]
      client/mysqltest.cc:1388(close_connections())[0x5a878a]
      client/mysqltest.cc:1436(free_used_memory())[0x5a8a00]
      client/mysqltest.cc:1478(cleanup_and_exit)[0x5a8c02]
      client/mysqltest.cc:9690(timer_output)[0x5b98f6]
      /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)[0x7f2d6da12ead]
      /data/repo/git/10.0/libmysqld/examples/mysqltest_embedded[0x5a72f9]

      According to buildbot, connect tests are also affected, maybe others too, the test run just gives up before reaching anything else.

      Note: sys_vars.log_error_func and sys_vars.log_error_func2 which fail in buildbot with "mysqltest failed but provided no output" are in fact the same ""Assertion `status_var.memory_used == 0' failed", but probably because they use non-default error log, MTR doesn't detect the failure correctly.

      I remember we agreed before not to pay much attention to this assertion failure, but then we need to decide whether we should disable the test run, or run --ps --embedded on a non-debug build, or do anything else about it.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                holyfoot Alexey Botchkov
                Reporter:
                elenst Elena Stepanova
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: