1. 12 Oct, 2006 7 commits
  2. 11 Oct, 2006 4 commits
    • unknown's avatar
      Fixes for embedded server test · d6d46923
      unknown authored
      
      client/mysqltest.c:
        Fix typo
      d6d46923
    • unknown's avatar
      mtr_im_stop returns 1 if all is well · 6c0ad741
      unknown authored
      6c0ad741
    • unknown's avatar
      Improve restart logic all code to detect restart is now in the functions · a0081378
      unknown authored
      'run_testcase_need_master/slave_restart'
      Remove the faulty qw
      Only look for mysql_fix_privilege_tables if not windows
      
      
      mysql-test/lib/mtr_cases.pl:
        Move all code to determine when to restart into 'run_testcase_need_master/slave_restart' 
        Add possibility to wite --force-restart in -master.opt file, this will force a restart and
        since master is not started with any special options there is no need to restart
        again afterwards.
      mysql-test/mysql-test-run.pl:
        Remove the qw surrounding ENV{'LD_LIBRARY_PATH'}
        Only look for the sh script mysql_fix_privileges when not on windows
        Remove warnings about using unitialized variables
        Improve the restart logic, eall code to determine when to restart is
        now in run_testcase_need_master_restart and run_testcase_need_slave_restart
      mysql-test/t/bdb-alter-table-2-master.opt:
        Use --force-restart
      mysql-test/t/not_embedded_server-master.opt:
        Use --force-restart
      a0081378
    • unknown's avatar
      Fix some bad code in mysqltest.c which cause segfault · 3caef95e
      unknown authored
      
      client/mysqltest.c:
        Remove vsnprintf() and DBUG_PRINT from die() function, as it's not portable to Windows, and it's not allowed to
        call vsnprintf() and then vfprintf() with the same args.
        Can't just print the buffer here, because the buffer is a fixed size.
        If the message is longer than will fit int he buffer, it would get
        truncated on Unix, and the full thing would be printed on Windows.
        This DBUG_PRINT isn't important enough for this hassle, so just get rid
        of it.
      3caef95e
  3. 08 Oct, 2006 6 commits
  4. 07 Oct, 2006 5 commits
  5. 06 Oct, 2006 8 commits
  6. 05 Oct, 2006 10 commits
    • unknown's avatar
      Rename "snapshot_setup" to "datadir_setup" as that is what is done by it. · 1822065d
      unknown authored
      Move call f dunction into "initialize_servers" so it's called also
      in stress and bench mode
      
      
      1822065d
    • unknown's avatar
      Add printout of file in which warning was detected · 78c5bc62
      unknown authored
      Cleanup .progress, .reject, .log and .warnings files produced by mysqltest
      
      
      client/mysqltest.c:
        Add printout of file in which warning was detected
      mysql-test/include/ctype_like_escape.inc:
        Remove warnings, convert -- comments to # comments
      mysql-test/mysql-test-run.pl:
        Cleanup all files produced by mysqltest before starting mysqltest again
      78c5bc62
    • unknown's avatar
    • unknown's avatar
      7ec1a292
    • unknown's avatar
      Open input file with "<" not ">>" · c3997a66
      unknown authored
      c3997a66
    • unknown's avatar
      Add policy directive about keeping mysqltest framework tools identical in all versions · 93a9883b
      unknown authored
      
      mysql-test/mysql-test-run.pl:
        Add policy directive about keeping mysqltest framework tools identical in all versions
        Cleanup the initial comment to reflect current state
      93a9883b
    • unknown's avatar
      No need to pass --valgrind to mysqltest anymore, the simple task of · 16b9d8d1
      unknown authored
      creating an environment variable is handled directly from the perl code.  
      
      
      16b9d8d1
    • unknown's avatar
      Make use of $opt_mem" and let 4.1 allow --vardir to be set. Still relies on the var/ directory · 2430d73c
      unknown authored
      but having it on tmpfs gives a big speedup. 
      
      
      mysql-test/mysql-test-run.pl:
        Make use of opt_mem and let 4.1 allow vardir to be set. Still relies on the var/ directory
        but having it on tmpfs gives a big speedup.
      2430d73c
    • unknown's avatar
      Use same --slave-load-tmpdir in all versions(backport from 5.0) · 9ba3b3f2
      unknown authored
      
      mysql-test/mysql-test-run.pl:
        Use same location for slave-load-tmpdir in all versions
      mysql-test/mysql-test-run.sh:
        Use same location for slave-load-tmpdir in all versions
      mysql-test/r/rpl_loaddata.result:
        Update result after changing slave-load-tmpdir to use a shorter path
      mysql-test/r/rpl_loaddatalocal.result:
        Update result after changing slave-load-tmpdir to use a shorter path
      mysql-test/r/rpl_log.result:
        Update result after changing slave-load-tmpdir to use a shorter path
      mysql-test/t/rpl_loaddatalocal.test:
        Use MYSQLTEST_VARDIR when specifying path to load from(backport from 5.0)
        Use new command "remove_file" instead of s"ystem rm"
      9ba3b3f2
    • unknown's avatar
      Bug #20010 mysql-test-run.pl: --record and --require conflict (test fails) · 6d89bcbc
      unknown authored
      - When --record is passed to mysqltest the whole testcase should be executed
      as it normally is while the output form the test is acumulating
      in ds_res. When test has finished ds_res should simply be written to the
      specified result file(if any) instead of comapring it against the result file.
      Simplify handling of --require and also the cecking of result files by splitting
      check_result function into one  function 'check_require' that is specialised in
      checking require's and leave 'check_result' to do just that.
      - "mysqltest --record" has been considered unsafe, but with this really simple
      logic, it should be safe to use.
      
      
      client/mysqltest.c:
        When --record is passed to mysqltest the whole testcase should be executed
        as it normally is while the output form the test is acumulating
        in ds_res. When test has finished ds_res should simply be written to the
        specified result file(if any) instead of comapring it against the result file.
        Simplify handling of --require and also the cecking of result files by splitting
        check_result function into one  function 'check_require' that is specialised in
        checking require's and leave 'check_result' to do just that.
      6d89bcbc