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

Cannot build the package under Debian Wheezy

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 5.5.35
    • 10.0.8
    • None
    • None
    • Debian Wheezy (7.3), amd64

    Description

      I'm trying to build MariaDB 5.5.35 packages under Debian Wheeze from the source package mariadb-5.5_5.5.35+maria-1~wheezy. Unfortunately the build process fails in the preparation to running tests. The error is shown below.

      MariaDB 5.5.34 builds fine on the very same system.

      Running tests
      OS=Linux
      Logging: ./mysql-test-run.pl  --force
      vardir: /home/packages/mariadb-5.5/mariadb-5.5-5.5.35+maria/builddir/mysql-test/var
      Removing old var directory...
      Creating var directory '/home/packages/mariadb-5.5/mariadb-5.5-5.5.35+maria/builddir/mysql-test/var'...
      Checking supported features...
      ** ERROR: Could not find '*' in
       at lib/mtr_cases.pm line 339
      make[4]: *** [mysql-test/CMakeFiles/test-force] Error 2

      Attachments

        Activity

          Maybe the tile for this bug report should be "Debian builds of 5.5.35 failing due to test failures".

          About the original '** ERROR: Could not find '*' in at lib/mtr_cases.pm line 339' issue:

          It was visible in all previous builds before https://github.com/ottok/mariadb-5.5/commit/73eea9f and hasn't been visible since. If you don't see any regressions in the build logs (many links below) then the issue is fixed.

          About the replace_result and $USER issue:

          All tests now pass on my laptop in the latest run: http://labs.seravo.fi/~otto/mariadb-repo/logs/mariadb-5.5_5.5.35-1_amd64.build-a82d59a-laptop.log
          The rpl.rpl_set_null_innodb fail I had yesterday on the laptop went away with no fixes, I assume it was a sporadic fail, I have seen it only ever once.

          About the unix_socket issue:

          When disabling tests I was able to build binary packages at http://labs.seravo.fi/~otto/mariadb-repo/?C=M;O=D for amd64: precise, trusty, wheezy, sid and for i386: precise. The other i386 fails due to TokuDB which does not build under i386 and pbuilder environment where the cmake if CMAKE_SYSTEM_PROCESSOR=amd64 does not detect pbuilder target processor correctly. I will now relaunch all of these to confirm that unix_socket issue is consistent (and not sporadic). If it helps, at least there are now binaries for the same revision which you can download and run the mariadb-test suite for binaries.

          About TokuDB tests:

          At https://launchpad.net/~mysql-ubuntu/+archive/mariadb/+packages (all builds at https://launchpad.net/~mysql-ubuntu/+archive/mariadb/+builds?build_text=&build_state=all) I have built successfully binary packages for precise and trusty when tests where disabled. When tests are enabled and I submitted saucy version for building, the i386 passes all tests and is successfull but the amd64 version fails in tokudb tests: https://launchpadlibrarian.net/164958444/buildlog_ubuntu-saucy-amd64.mariadb-5.5_5.5.35-1~saucy1~ppa2_FAILEDTOBUILD.txt.gz

          This seems consistent for Launchpad (buildd) and is visible in a previous trusty/amd64 build too but not in my plain laptop or in pbuilder.

          otto Otto Kekäläinen added a comment - Maybe the tile for this bug report should be "Debian builds of 5.5.35 failing due to test failures". About the original '** ERROR: Could not find '*' in at lib/mtr_cases.pm line 339' issue: It was visible in all previous builds before https://github.com/ottok/mariadb-5.5/commit/73eea9f and hasn't been visible since. If you don't see any regressions in the build logs (many links below) then the issue is fixed. About the replace_result and $USER issue: All tests now pass on my laptop in the latest run: http://labs.seravo.fi/~otto/mariadb-repo/logs/mariadb-5.5_5.5.35-1_amd64.build-a82d59a-laptop.log The rpl.rpl_set_null_innodb fail I had yesterday on the laptop went away with no fixes, I assume it was a sporadic fail, I have seen it only ever once. About the unix_socket issue: When disabling tests I was able to build binary packages at http://labs.seravo.fi/~otto/mariadb-repo/?C=M;O=D for amd64: precise, trusty, wheezy, sid and for i386: precise. The other i386 fails due to TokuDB which does not build under i386 and pbuilder environment where the cmake if CMAKE_SYSTEM_PROCESSOR=amd64 does not detect pbuilder target processor correctly. I will now relaunch all of these to confirm that unix_socket issue is consistent (and not sporadic). If it helps, at least there are now binaries for the same revision which you can download and run the mariadb-test suite for binaries. About TokuDB tests: At https://launchpad.net/~mysql-ubuntu/+archive/mariadb/+packages (all builds at https://launchpad.net/~mysql-ubuntu/+archive/mariadb/+builds?build_text=&build_state=all ) I have built successfully binary packages for precise and trusty when tests where disabled. When tests are enabled and I submitted saucy version for building, the i386 passes all tests and is successfull but the amd64 version fails in tokudb tests: https://launchpadlibrarian.net/164958444/buildlog_ubuntu-saucy-amd64.mariadb-5.5_5.5.35-1~saucy1~ppa2_FAILEDTOBUILD.txt.gz This seems consistent for Launchpad (buildd) and is visible in a previous trusty/amd64 build too but not in my plain laptop or in pbuilder.
          elenst Elena Stepanova added a comment - - edited

          Maybe the tile for this bug report should be "Debian builds of 5.5.35 failing due to test failures".

          This bug report was created by its author specifically about "** ERROR: Could not find '*' in" failure, and will stay as such.
          The fix for it is removal of extra copying from debian/dist/*/rules. Upon your request, I did not push it to 5.5 tree, it's waiting for the batch of your changes.
          The fix has been pushed to 10.0 tree here: http://bazaar.launchpad.net/~maria-captains/maria/10.0/revision/3975
          The bug report will now be closed.
          Other failures, if they need to be fixed on MariaDB side, should be filed separately.

          About the original '** ERROR: Could not find '*' in at lib/mtr_cases.pm line 339' issue:
          It was visible in all previous builds before https://github.com/ottok/mariadb-5.5/commit/73eea9f and hasn't been visible since. If you don't see any regressions in the build logs (many links below) then the issue is fixed.

          No, the failure "ERROR: Could not find '*' in" has nothing to do with the change in unix_socket file. Maybe you pasted a wrong link.

          About the replace_result and $USER issue:
          All tests now pass on my laptop in the latest run: http://labs.seravo.fi/~otto/mariadb-repo/logs/mariadb-5.5_5.5.35-1_amd64.build-a82d59a-laptop.log

          This failure was fixed by the change https://github.com/ottok/mariadb-5.5/commit/73eea9f.
          It will be pushed to maria/5.5 tree and merged up to 10.0 tree.

          elenst Elena Stepanova added a comment - - edited Maybe the tile for this bug report should be "Debian builds of 5.5.35 failing due to test failures". This bug report was created by its author specifically about "** ERROR: Could not find '*' in" failure, and will stay as such. The fix for it is removal of extra copying from debian/dist/*/rules. Upon your request, I did not push it to 5.5 tree, it's waiting for the batch of your changes. The fix has been pushed to 10.0 tree here: http://bazaar.launchpad.net/~maria-captains/maria/10.0/revision/3975 The bug report will now be closed. Other failures, if they need to be fixed on MariaDB side, should be filed separately. About the original '** ERROR: Could not find '*' in at lib/mtr_cases.pm line 339' issue: It was visible in all previous builds before https://github.com/ottok/mariadb-5.5/commit/73eea9f and hasn't been visible since. If you don't see any regressions in the build logs (many links below) then the issue is fixed. No, the failure "ERROR: Could not find '*' in" has nothing to do with the change in unix_socket file. Maybe you pasted a wrong link. About the replace_result and $USER issue: All tests now pass on my laptop in the latest run: http://labs.seravo.fi/~otto/mariadb-repo/logs/mariadb-5.5_5.5.35-1_amd64.build-a82d59a-laptop.log This failure was fixed by the change https://github.com/ottok/mariadb-5.5/commit/73eea9f . It will be pushed to maria/5.5 tree and merged up to 10.0 tree.

          The fix with removal of cp lines was pushed to 10.0 tree:
          http://bazaar.launchpad.net/~maria-captains/maria/10.0/revision/3975

          5.5 tree should be fixed separately by upcoming Otto's changes.

          elenst Elena Stepanova added a comment - The fix with removal of cp lines was pushed to 10.0 tree: http://bazaar.launchpad.net/~maria-captains/maria/10.0/revision/3975 5.5 tree should be fixed separately by upcoming Otto's changes.
          karpa13a Mihail Karp added a comment -

          same on 5.5.36

          karpa13a Mihail Karp added a comment - same on 5.5.36

          That's expected, as said in the comment (and in the Fix Versions field), the fix was only pushed in 10.0, while 5.5 is awaiting package refactoring which is currently being performed.

          elenst Elena Stepanova added a comment - That's expected, as said in the comment (and in the Fix Versions field), the fix was only pushed in 10.0, while 5.5 is awaiting package refactoring which is currently being performed.

          People

            elenst Elena Stepanova
            jorgus Szymon Juraszczyk
            Votes:
            1 Vote for this issue
            Watchers:
            5 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.