(mysql.info.gz) Reporting mysqltest bugs

Info Catalog

(mysql.info.gz) extending mysqltest

(mysql.info.gz) MySQL test suite

 
 25.1.2.3 Reporting Bugs in the MySQL Test Suite
 ...............................................
 
 If your MySQL version doesn't pass the test suite you should do the
 following:
 
    * Don't send a bug report before you have found out as much as
      possible of what when wrong!  When you do it, please use the
      `mysqlbug' script so that we can get information about your system
      and MySQL version.  Bug reports.
 
    * Make sure to include the output of `mysql-test-run', as well as
      contents of all `.reject' files in `mysql-test/r' directory.
 
    * If a test in the test suite fails, check whether the test fails
      also when run by its own:
 
           cd mysql-test
           mysql-test-run --local test-name
 
      If this fails, then you should configure MySQL with `--with-debug'
      and run `mysql-test-run' with the `--debug' option. If this also
      fails send the trace file `var/tmp/master.trace' to
      `ftp://ftp.mysql.com/pub/mysql/upload/' so that we can examine it.
      Please remember to also include a full description of your system,
      the version of the mysqld binary and how you compiled it.
 
    * Try also to run `mysql-test-run' with the `--force' option to see
      whether there is any other test that fails.
 
    * If you have compiled MySQL yourself, check our manual for how to
      compile MySQL on your platform or, preferable, use one of the
      binaries we have compiled for you at
      `http://dev.mysql.com/downloads/'.  All our standard binaries
      should pass the test suite !
 
    * If you get an error, like `Result length mismatch' or `Result
      content mismatch' it means that the output of the test didn't match
      exactly the expected output. This could be a bug in MySQL or that
      your mysqld version produces slight different results under some
      circumstances.
 
      Failed test results are put in a file with the same base name as
      the result file with the `.reject' extension.  If your test case is
      failing, you should do a diff on the two files.  If you cannot see
      how they are different, examine both with `od -c' and also check
      their lengths.
 
    * If a test fails totally, you should check the logs file in the
      `mysql-test/var/log' directory for hints of what went wrong.
 
    * If you have compiled MySQL with debugging you can try to debug this
      by running `mysql-test-run' with the `--gdb' and/or `--debug'
      options.   Making trace files.
 
      If you have not compiled MySQL for debugging you should probably
      do that.  Just specify the `--with-debug' options to `configure'!
       Installing source.
 

Info Catalog

(mysql.info.gz) extending mysqltest

(mysql.info.gz) MySQL test suite