An error occurred fetching the project authors.
  1. 16 Jun, 2008 1 commit
    • Matthias Leich mleich@mysql.com's avatar
      Fix for · 00c19cd8
      Matthias Leich mleich@mysql.com authored
         Bug#37167 funcs_1: Many tests fail if the embedded server is used.
         Bug#37164 funcs_1: Some tests fail if an optional character set is missing.
      + some cleanup within the testsuite related to the fixes above
      + some adjustments to open bugs on Mac OS X
      
      Details:
      - Remove the initial loading of data from tests if these data
        are not somewhere retrieved
      - Remove any use of columns with attribute unicode
        (-> UCS2 is no more needed) from tests where unicode
        properties are not checked or somehow required
      - Create a separate branch of the Character maximum length test
        (CML). If UCS2 is available than this test gets applied to
        every available type of string column with attribute unicode
        This prevents any loss of coverage by the points above.
      - Disable the execution of is_tables_ndb which gives wrong
        results because of a bug. Correct the exepected results of
        this test.
      - In case of tests failing when applied to the embedded server
          1) Create a variant of this test for the embedded server
        or
          2) Skip the test in case of embedded server
        depending on purpose and complexity of test.
      - Skip the tests which could suffer from
        Bug 28309 First insert violates unique constraint - was "memory" table empty ?
        Bug 37380 Test funcs_1.is_columns_myisam_embedded fails on OS X
        (both bugs Mac OS X, embedded server, MySQL 5.0 only)
      - Minor improvements like remove typos
      00c19cd8
  2. 23 Apr, 2008 1 commit
    • kent@mysql.com/kent-amd64.(none)'s avatar
      Many files: [Changes done by mleich] · 3cf72be6
      kent@mysql.com/kent-amd64.(none) authored
        Fix for
           Bug#35335 funcs_1: Some tests fail within load_file during
                              pushbuild runs
           Solution: 1. Move files with input data used in load_file,
                        load data etc.
                        from suite/funcs_1/<whatever>
                        to std_data
                     2. Use for testsuite funcs_1 the server option
                        --secure-file-priv=<MYSQLTEST_VARDIR>
                     3. Outfiles have to be stored under MYSQLTEST_VARDIR
        + changes according to WL#4304 Cleanup in funcs_1 tests
          - backport of fixes/improvements made in 5.1 to 5.0
            The differences between scripts in 5.0 and 5.1 cause
            much additional and annoying work during any upmerge.
          - replace error numbers with names
          - improved comments
          - improved formatting
          - Unify storage engine names so that result files for
            storage engine variants do not differ (some tests)
          - remove a script no more used (tests are done in other scripts)
      3cf72be6
  3. 31 Mar, 2008 1 commit
    • mleich@five.local.lan's avatar
      Fix for · 89ddc0aa
      mleich@five.local.lan authored
         Bug#35335 funcs_1: Some tests fail within load_file during
                            pushbuild runs
         Solution: 1. Move files with input data used in load_file, 
                      load data etc. 
                      from suite/funcs_1/<whatever>
                      to std_data
                   2. Use for testsuite funcs_1 the server option
                      --secure-file-priv=<MYSQLTEST_VARDIR>
                   3. Outfiles have to be stored under MYSQLTEST_VARDIR 
      + changes according to WL#4304 Cleanup in funcs_1 tests
        - backport of fixes/improvements made in 5.1 to 5.0
          The differences between scripts in 5.0 and 5.1 cause
          much additional and annoying work during any upmerge.
        - replace error numbers with names
        - improved comments
        - improved formatting
        - Unify storage engine names so that result files for
          storage engine variants do not differ (some tests)
        - remove a script no more used (tests are done in other scripts)
      89ddc0aa
  4. 07 Mar, 2008 1 commit
    • mleich@five.local.lan's avatar
      WL#4203 Reorganize and fix the data dictionary tests of · 30091e23
      mleich@five.local.lan authored
              testsuite funcs_1
      1. Fix the following bugs
         Bug#30440 "datadict" tests (all engines) fail: Character sets depend on configuration
            Solution: Test variants charset_collation_* adjusted to different builds
         Bug#32603 "datadict" tests (all engines) fail in "community" tree: "PROFILING" table
            Solution: Excluding "PROFILING" table from queries
         Bug#33654 "slow log" is missing a line
            Solution: Unify the content of the fields TABLES.TABLE_ROWS and
                      STATISTICS.CARDINALITY within result sets
         Bug#34532 Some funcs_1 tests do not clean up at end of testing
            Solution: DROP objects/reset global server variables modified during testing
                      + let tests missing implementation end before loading of tables
         Bug#31421 funcs_1: ndb__datadict fails, discrepancy between scripts and expected results
            Solution: Cut <engine>__datadict tests into smaller tests + generate new results.
         Bug#33599 INFORMATION_SCHEMA.STATISTICS got a new column INDEX_COMMENT: tests fail (2)
            Generation of new results during post merge fix
         Bug#33600 CHARACTER_OCTET_LENGTH is now CHARACTER_MAXIMUM_LENGTH * 4
            Generation of new results during post merge fix
         Bug#33631 Platform-specific replace of CHARACTER_MAXIMUM_LENGTH broken by 4-byte encoding
            Generation of new results during post merge fix
            + removal of platform-specific replace routine (no more needed)
      2. Restructure the tests
         - Test not more than one INFORMATION_SCHEMA view per testscript
         - Separate tests of I_S view layout+functionality from content related to the
           all time existing databases "information_schema", "mysql" and "test"
         - Avoid storage engine related variants of tests which are not sensible to
           storage engines at all.
      3. Reimplement or add some subtests + cleanup
         There is a some probability that even the reviewed changeset
         - does not fix all bugs from above   or
         - contains new bugs which show up on some platforms <> Linux or on one of
           the various build types
      4. The changeset contains fixes according to
         - one code review
         - minor bugs within testing code found after code review (accepted by reviewer)
         - problems found during tests with 5.0.56 in build environment
      30091e23
  5. 06 Feb, 2007 1 commit