An error occurred fetching the project authors.
  1. 27 Jun, 2007 1 commit
    • unknown's avatar
      WL#3303 · bd4ac4b3
      unknown authored
      - undoing disable of ndb tests
      
      
      bd4ac4b3
  2. 14 Jun, 2007 1 commit
    • unknown's avatar
      WL#3303 (RBR: Engine-controlled logging format): · f3dc0478
      unknown authored
      Test case fixes.
      
      
      mysql-test/r/binlog_multi_engine.result:
        Result change.
      mysql-test/r/rpl_ndb_stm_innodb.result:
        Result change.
      mysql-test/t/binlog_multi_engine.test:
        NDB tests only work in MIXED or ROW mode. Adding some cleanup actions.
      mysql-test/t/loaddata_autocom_ndb.test:
        NDB requires MIXED or ROW mode.
      mysql-test/t/ndb_alter_table.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_alter_table2.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_alter_table3.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_autodiscover.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_autodiscover2.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_autodiscover3.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_basic.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_binlog_log_bin.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_binlog_multi.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_bitfield.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_blob.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_blob_partition.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_cache.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_cache2.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_cache_multi.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_cache_multi2.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_charset.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_condition_pushdown.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_config.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_config2.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_cursor.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_database.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_dd_alter.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_dd_backuprestore.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_dd_basic.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_dd_ddl.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_dd_disk2memory.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_dd_dump.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_dd_sql_features.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_gis.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_index.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_index_ordered.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_index_unique.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_insert.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_limit.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_loaddatalocal.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_lock.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_minmax.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_multi.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_partition_error.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_partition_key.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_partition_list.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_partition_range.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_read_multi_range.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_rename.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_replace.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_restore.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_restore_partition.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_restore_print.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_row_format.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_single_user.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_sp.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_subquery.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_temporary.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_transaction.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_trigger.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_truncate.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_types.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_update.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndb_view.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ndbapi.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/ps_7ndb.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/rpl_ndb_commit_afterflush.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/rpl_ndb_innodb_trans.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      mysql-test/t/rpl_ndb_stm_innodb.test:
        We need MIXED mode on slave since it is necessary to let the slave
        switch to row format when executing replicated statements.
      mysql-test/t/strict_autoinc_5ndb.test:
        NDB requires MIXED or ROW mode, but will switch to row format
        automatically, so we only run these tests under ROW mode.
      f3dc0478
  3. 16 Apr, 2007 1 commit
    • unknown's avatar
      Clear field_alloc when it's moved to result set (allows us to always call free_root on field_alloc) · 48892844
      unknown authored
      Change to use remove_file instead of 'system rm' in a lot of tests. (Should fix some windows test problems)
      Removed memory leak in mysql_test if sync_with_master fails.
      Do not terminate ndb_cluster_binary_log before the util thread has finnished. This should fix a shutdown bug where a thread is accessing injector_mutex after it's freed.
      Patch may fix Bug#27622 "mysqld shutdown, util thread continues, while binlog thread exits"
      
      
      client/mysqltest.c:
        Added missing 'mysql_free_result' (fixed confusing memory leak when sync_with_master fails)ug
      mysql-test/mysql-test-run.pl:
        Add the test case name to the instance manager log files
      mysql-test/r/rpl_log_pos.result:
        Made test more portable (for powermac)
      mysql-test/t/disabled.def:
        Disabled im_life_cycle (added bug#27851)
      mysql-test/t/myisam-system.test:
        Use remove_file instead of "system rm"
      mysql-test/t/ndb_autodiscover.test:
        Use remove_file instead of "system rm"
      mysql-test/t/ndb_loaddatalocal.test:
        Use remove_file instead of "system rm"
      mysql-test/t/rpl_loaddatalocal.test:
        Use remove_file instead of "system rm"
      mysql-test/t/rpl_log_pos.test:
        Made test more portable (for powermac)
      mysql-test/t/rpl_misc_functions.test:
        Use remove_file instead of "system rm"
      mysql-test/t/rpl_rbr_to_sbr.test:
        Use remove_file instead of "system rm"
      mysql-test/t/rpl_row_NOW.test:
        Use remove_file instead of "system rm"
      mysql-test/t/rpl_row_sp001.test:
        Use remove_file instead of "system rm"
      mysql-test/t/rpl_row_sp011.test:
        Use remove_file instead of "system rm"
      mysql-test/t/show_check.test:
        Use remove_file instead of "system rm"
      mysys/my_alloc.c:
        Don't return on zero argument, as this may hide other errors
      server-tools/instance-manager/log.cc:
        Log errors to both stdout and stderr (to know in which context we got the error)
      server-tools/instance-manager/thread_registry.cc:
        Log error before common assert (to know in which context we fail)
      sql/ha_ndbcluster.cc:
        Do not terminate ndb_cluster_binary_log before the util thread has finnished.
      sql/ha_ndbcluster.h:
        Do not terminate ndb_cluster_binary_log before the util thread has finnished.
      sql/ha_ndbcluster_binlog.cc:
        Do not terminate ndb_cluster_binary_log before the util thread has finnished.
      sql-common/client.c:
        Clear field_alloc when it's moved to result set (allows us to always call free_root on field_alloc)
      48892844
  4. 14 Jun, 2006 1 commit
    • unknown's avatar
      Bug #19493 NDB does not ignore duplicate keys when using LOAD DATA LOCAL · ca1fd91f
      unknown authored
      - make sure to disable bulk insert when check for duplicate key is needed
      
      
      mysql-test/r/ndb_loaddatalocal.result:
        New BitKeeper file ``mysql-test/r/ndb_loaddatalocal.result''
      mysql-test/t/ndb_loaddatalocal.test:
        New BitKeeper file ``mysql-test/t/ndb_loaddatalocal.test''
      ca1fd91f