Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-4214

Building 5.5.29 sources one test fails: main.partition_rename_longfilename

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 5.5.29
    • 10.0.2, 5.5.31
    • None
    • None
    • Ubuntu 12.04

    Description

      I downloaded there official MariaDB release as tar.gz from mariadb.org and while trying to build it, one of the mysql-test failed: main.partition_rename_longfilename

      Running the individual test gives the following output:

      $ ./mysql-test-run main.partition_rename_longfilename
      Logging: ./mysql-test-run  main.partition_rename_longfilename
      vardir: /home/otto/MariaDB/mariadb-5.5-5.5.29/builddir/mysql-test/var
      Checking leftover processes...
       - found old pid 24625 in 'mysqld.3.pid', killing it...
         process did not exist!
      mysql-test-run: WARNING: Found non pid file 'mysqld.err' in '/home/otto/MariaDB/mariadb-5.5-5.5.29/builddir/mysql-test/var/run'
      mysql-test-run: WARNING: Found non pid file 'mytest.log' in '/home/otto/MariaDB/mariadb-5.5-5.5.29/builddir/mysql-test/var/run'
      Removing old var directory...
      Creating var directory '/home/otto/MariaDB/mariadb-5.5-5.5.29/builddir/mysql-test/var'...
      Checking supported features...
      MariaDB Version 5.5.29-MariaDB-mariadb1~precise
      Installing system database...
       - skipping ndbcluster
       - SSL connections supported
      Collecting tests...
      Using server port 59245
       
      ==============================================================================
       
      TEST                                      RESULT   TIME (ms) or COMMENT
      --------------------------------------------------------------------------
       
      worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 16000..16019
      main.partition_rename_longfilename       [ fail ]
              Test ended at 2013-02-27 23:24:42
       
      CURRENT_TEST: main.partition_rename_longfilename
      mysqltest: At line 28: query 'RENAME TABLE t1 TO `t2_............................end`' failed: 7: Error on rename of './test/t1#P#p0.MYI' to './test/t2_@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002eend#P#p0.MYI' (Errcode: 36)
       
      The result from queries just before the failure was:
      < snip >
      PARTITION p2 VALUES LESS THAN MAXVALUE);
      # List of files in database `test`, all original t1-files here
      t1#P#p0.MYD
      t1#P#p0.MYI
      t1#P#p1@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e.MYD
      t1#P#p1@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e.MYI
      t1#P#p2.MYD
      t1#P#p2.MYI
      t1.frm
      t1.par
      INSERT INTO t1 VALUES (1), (2), (3), (4), (5), (6), (7), (8), (9), (10);
      # Renaming to a file name where the first partition is 155 chars
      # and the second partition is 255 chars
      RENAME TABLE t1 TO `t2_............................end`;
       
      More results from queries before failure can be found in /home/otto/MariaDB/mariadb-5.5-5.5.29/builddir/mysql-test/var/log/partition_rename_longfilename.log
       
       - saving '/home/otto/MariaDB/mariadb-5.5-5.5.29/builddir/mysql-test/var/log/main.partition_rename_longfilename/' to '/home/otto/MariaDB/mariadb-5.5-5.5.29/builddir/mysql-test/var/log/main.partition_rename_longfilename/'
      --------------------------------------------------------------------------
      The servers were restarted 0 times
      Spent 0.000 of 4 seconds executing testcases
       
      Failure: Failed 1/1 tests, 0.00% were successful.
       
      Failing test(s): main.partition_rename_longfilename

      var/log/main.partition_rename_longfilename/ attached

      Attachments

        Activity

          The filename 't2_@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002eend#P#p0.MYI' is 155 characters long, and as I have my home folder encrypted using eCryptFS, filenames above 140 characters might be too long (as the encrypted version can't fit 255 characters).

          So this issues is indeed restricted to my setup. Normal users are very unlikely to run a MariaDB server on a eCryptFS partition and certainly binaries can be built on unenctypted partitions, so we can ignore this test error.

          otto Otto Kekäläinen added a comment - The filename 't2_@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002e@002eend#P#p0.MYI' is 155 characters long, and as I have my home folder encrypted using eCryptFS, filenames above 140 characters might be too long (as the encrypted version can't fit 255 characters). So this issues is indeed restricted to my setup. Normal users are very unlikely to run a MariaDB server on a eCryptFS partition and certainly binaries can be built on unenctypted partitions, so we can ignore this test error.

          From IRC:

          <montywi> otto_: ok; We should test that when MariaDB starts and disable this test if it can't create files with 255 characters.
          ...
          <montywi> better to use perl
          ...
          <montywi> so for the test, it's enough to check if we can create a 255 file name in datadir

          elenst Elena Stepanova added a comment - From IRC: <montywi> otto_: ok; We should test that when MariaDB starts and disable this test if it can't create files with 255 characters. ... <montywi> better to use perl ... <montywi> so for the test, it's enough to check if we can create a 255 file name in datadir
          elenst Elena Stepanova added a comment - - edited

          The change is currently in 5.5-elenst:
          http://bazaar.launchpad.net/~elenst/maria/5.5-elenst/revision/3686

          It will be pushed into maria/5.5 after release 5.5.30, since it's not urgent, to avoid disturbing the ongoing release process.

          elenst Elena Stepanova added a comment - - edited The change is currently in 5.5-elenst: http://bazaar.launchpad.net/~elenst/maria/5.5-elenst/revision/3686 It will be pushed into maria/5.5 after release 5.5.30, since it's not urgent, to avoid disturbing the ongoing release process.

          ok to push

          Regards,
          Sergei

          serg Sergei Golubchik added a comment - ok to push Regards, Sergei

          Thanks!

          elenst Elena Stepanova added a comment - Thanks!

          Pushed into maria/5.5 as revno 3697

          elenst Elena Stepanova added a comment - Pushed into maria/5.5 as revno 3697

          People

            elenst Elena Stepanova
            otto Otto Kekäläinen
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.