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

Tests in perfschema_stress suite either fail or don't clean up

    XMLWordPrintable

    Details

      Description

      elenst@jessie:/data/bld/10.1/mysql-test$ perl ./mtr --suite=perfschema_stress --force
      Logging: ./mtr  --suite=perfschema_stress --force
      vardir: /data/bld/10.1/mysql-test/var
      Checking leftover processes...
      Removing old var directory...
      Creating var directory '/data/bld/10.1/mysql-test/var'...
      Checking supported features...
      MariaDB Version 10.1.19-MariaDB-debug
       - SSL connections supported
       - binaries are debug compiled
      Using suites: perfschema_stress
      Collecting tests...
      Installing system database...
       
      ==============================================================================
       
      TEST                                      RESULT   TIME (ms) or COMMENT
      --------------------------------------------------------------------------
       
      worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 16000..16019
      perfschema_stress.modify                 [ pass ]   1236
       
      MTR's internal check of the test case 'perfschema_stress.modify' failed.
      This means that the test case does not preserve the state that existed
      before the test case was executed.  Most likely the test case did not
      do a proper clean-up. It could also be caused by the previous test run
      by this thread, if the server wasn't restarted.
      This is the diff of the states of the servers before and after the
      test case was executed:
      mysqltest: Logging to '/data/bld/10.1/mysql-test/var/tmp/check-mysqld_1.log'.
      mysqltest: Results saved in '/data/bld/10.1/mysql-test/var/tmp/check-mysqld_1.result'.
      mysqltest: Connecting to server localhost:16000 (socket /data/bld/10.1/mysql-test/var/tmp/mysqld.1.sock) as 'root', connection 'default', attempt 0 ...
      mysqltest: ... Connected.
      mysqltest: Start processing test commands from './include/check-testcase.test' ...
      mysqltest: ... Done processing test commands.
      --- /data/bld/10.1/mysql-test/var/tmp/check-mysqld_1.result	2016-10-09 23:04:37.240502389 +0300
      +++ /data/bld/10.1/mysql-test/var/tmp/check-mysqld_1.reject	2016-10-09 23:04:38.736502382 +0300
      @@ -470,6 +470,7 @@
       def	performance_schema	utf8	utf8_general_ci	NULL
       def	test	latin1	latin1_swedish_ci	NULL
       tables_in_test
      +t1
       tables_in_mysql
       mysql.columns_priv
       mysql.column_stats
       
      mysqltest: Result length mismatch
       
      not ok
       
      perfschema_stress.read                   [ fail ]
              Test ended at 2016-10-09 23:04:39
       
      CURRENT_TEST: perfschema_stress.read
      mysqltest: At line 12: query 'SELECT * FROM performance_schema.processlist p,
      performance_schema.events_waits_current e
      WHERE p.THREAD_ID = e.THREAD_ID
      AND TIMER_START = 0
      ORDER BY e.EVENT_ID' failed: 1146: Table 'performance_schema.processlist' doesn't exist
       
      The result from queries just before the failure was:
      SELECT * FROM performance_schema.setup_instruments
      WHERE ENABLED='NO' AND TIMED='NO';
      NAME	ENABLED	TIMED
      SELECT * FROM performance_schema.events_waits_current
      WHERE (TIMER_END - TIMER_START != TIMER_WAIT);
      THREAD_ID	EVENT_ID	END_EVENT_ID	EVENT_NAME	SOURCE	TIMER_START	TIMER_END	TIMER_WAIT	SPINS	OBJECT_SCHEMA	OBJECT_NAME	INDEX_NAME	OBJECT_TYPE	OBJECT_INSTANCE_BEGIN	NESTING_EVENT_ID	NESTING_EVENT_TYPE	OPERATION	NUMBER_OF_BYTES	FLAGS
      SELECT * FROM performance_schema.events_waits_history
      WHERE SPINS != NULL;
      THREAD_ID	EVENT_ID	END_EVENT_ID	EVENT_NAME	SOURCE	TIMER_START	TIMER_END	TIMER_WAIT	SPINS	OBJECT_SCHEMA	OBJECT_NAME	INDEX_NAME	OBJECT_TYPE	OBJECT_INSTANCE_BEGIN	NESTING_EVENT_ID	NESTING_EVENT_TYPE	OPERATION	NUMBER_OF_BYTES	FLAGS
      SELECT * FROM performance_schema.processlist p,
      performance_schema.events_waits_current e
      WHERE p.THREAD_ID = e.THREAD_ID
      AND TIMER_START = 0
      ORDER BY e.EVENT_ID;
       
       - saving '/data/bld/10.1/mysql-test/var/log/perfschema_stress.read/' to '/data/bld/10.1/mysql-test/var/log/perfschema_stress.read/'
      perfschema_stress.setup                  [ fail ]
              Test ended at 2016-10-09 23:04:40
       
      CURRENT_TEST: perfschema_stress.setup
      mysqltest: The test didn't produce any output
       
       - saving '/data/bld/10.1/mysql-test/var/log/perfschema_stress.setup/' to '/data/bld/10.1/mysql-test/var/log/perfschema_stress.setup/'
      perfschema_stress.work                   [ pass ]    130
       
      MTR's internal check of the test case 'perfschema_stress.work' failed.
      This means that the test case does not preserve the state that existed
      before the test case was executed.  Most likely the test case did not
      do a proper clean-up. It could also be caused by the previous test run
      by this thread, if the server wasn't restarted.
      This is the diff of the states of the servers before and after the
      test case was executed:
      mysqltest: Logging to '/data/bld/10.1/mysql-test/var/tmp/check-mysqld_1.log'.
      mysqltest: Results saved in '/data/bld/10.1/mysql-test/var/tmp/check-mysqld_1.result'.
      mysqltest: Connecting to server localhost:16000 (socket /data/bld/10.1/mysql-test/var/tmp/mysqld.1.sock) as 'root', connection 'default', attempt 0 ...
      mysqltest: ... Connected.
      mysqltest: Start processing test commands from './include/check-testcase.test' ...
      mysqltest: ... Done processing test commands.
      --- /data/bld/10.1/mysql-test/var/tmp/check-mysqld_1.result	2016-10-09 23:04:40.508502374 +0300
      +++ /data/bld/10.1/mysql-test/var/tmp/check-mysqld_1.reject	2016-10-09 23:04:40.808502372 +0300
      @@ -470,6 +470,7 @@
       def	performance_schema	utf8	utf8_general_ci	NULL
       def	test	latin1	latin1_swedish_ci	NULL
       tables_in_test
      +t1
       tables_in_mysql
       mysql.columns_priv
       mysql.column_stats
       
      mysqltest: Result length mismatch
       
      not ok
       
      --------------------------------------------------------------------------
      The servers were restarted 3 times
      Spent 1.366 of 11 seconds executing testcases
       
      Check of testcase failed for: perfschema_stress.work perfschema_stress.modify
       
      Completed: Failed 2/4 tests, 50.00% were successful.
       
      Failing test(s): perfschema_stress.read perfschema_stress.setup
       
      The log files in var/log may give you some hint of what went wrong.
       
      If you want to report this error, please read first the documentation
      at http://dev.mysql.com/doc/mysql/en/mysql-test-suite.html
       
      mysql-test-run: *** ERROR: there were failing test cases
      

        Attachments

          Activity

            People

            • Assignee:
              elenst Elena Stepanova
              Reporter:
              elenst Elena Stepanova
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: