An error occurred fetching the project authors.
  1. 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
  2. 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
  3. 27 Jul, 2007 1 commit
    • joerg@debian.(none)'s avatar
      Fix a bad BitKeeper dependency structure for the "funcs_1" suite: · c80ced41
      joerg@debian.(none) authored
      The files below "mysql-test/suite/funcs_1" in version 5.1
      did not depend on the equivalent ones in 5.0,
      probably because they had been checked in independent of each other
      in both versions.
      
      Step 1:
      Foreach file F in the suite that has a "deleted" counterpart D, use
          bk rm $F
          bk mv $D $F
      to get those files into the 5.1 suite that (for BK) depend on 5.0.
      c80ced41
  4. 06 Feb, 2007 2 commits