Details

    Description

      elenst in MDEV-10261 said:

      Apparently it doesn't run in buildbot at all. The only builders where we have default suites to run with --big are fulltests, and they don't build TokuDB because cmake version is too low.

      Attachments

        Activity

          danblack Daniel Black created issue -
          danblack Daniel Black made changes -
          Field Original Value New Value
          Summary Build bots (x86_64) cable of running tokudb --big-tests Build bots (x86_64) capable of running tokudb --big-tests
          danblack Daniel Black added a comment -

          from MDEV-10708 tokudb test tokudb_parts.partition_alter4_tokudb needs >=20 mins

           export MTR_TESTCASE_TIMEOUT=20
          

          danblack Daniel Black added a comment - from MDEV-10708 tokudb test tokudb_parts.partition_alter4_tokudb needs >=20 mins export MTR_TESTCASE_TIMEOUT=20
          danblack Daniel Black added a comment -

          test case fixes:

          https://github.com/MariaDB/server/pull/231 (against 10.0) rows-32m-rand-insert
          https://github.com/MariaDB/server/pull/229 (against 10.2) tokudb_parts suite

          danblack Daniel Black added a comment - test case fixes: https://github.com/MariaDB/server/pull/231 (against 10.0) rows-32m-rand-insert https://github.com/MariaDB/server/pull/229 (against 10.2) tokudb_parts suite
          elenst Elena Stepanova made changes -
          Assignee Daniel Bartholomew [ dbart ] Elena Stepanova [ elenst ]

          Increasing timeout does not solve anything. We can't afford running big tests in all builders on every push, it will be insanely slow. There are and will be only a few separate test runs for big tests, for which the timeout has already been increased. The problem of this task is that these test runs for big tests are currently performed on the machine which is incapable of building TokuDB.

          elenst Elena Stepanova added a comment - Increasing timeout does not solve anything. We can't afford running big tests in all builders on every push, it will be insanely slow. There are and will be only a few separate test runs for big tests, for which the timeout has already been increased. The problem of this task is that these test runs for big tests are currently performed on the machine which is incapable of building TokuDB.
          danblack Daniel Black added a comment -

          ok. makes sense. Thanks elenst

          danblack Daniel Black added a comment - ok. makes sense. Thanks elenst
          danblack Daniel Black added a comment -

          kvm-fulltest2-big slaves now have cmake-3.5.1. Looks like this could succeed once other errors are fixed.

          http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2-big

          danblack Daniel Black added a comment - kvm-fulltest2-big slaves now have cmake-3.5.1. Looks like this could succeed once other errors are fixed. http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2-big
          serg Sergei Golubchik made changes -
          Summary Build bots (x86_64) capable of running tokudb --big-tests run tokudb --big-tests in buildbot

          If it hasn't been done yet, I don't think it's worth doing now. Hopefully we'll get rid of TokuDB by the next version.

          elenst Elena Stepanova added a comment - If it hasn't been done yet, I don't think it's worth doing now. Hopefully we'll get rid of TokuDB by the next version.
          elenst Elena Stepanova made changes -
          Fix Version/s N/A [ 14700 ]
          Resolution Won't Fix [ 2 ]
          Status Open [ 1 ] Closed [ 6 ]
          serg Sergei Golubchik made changes -
          Workflow MariaDB v3 [ 76862 ] MariaDB v4 [ 132933 ]

          People

            elenst Elena Stepanova
            danblack Daniel Black
            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.