Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Fix
    • 10.2.0
    • 5.5.62
    • Tests
    • None
    • Ubuntu 14.04+, macOS 10.13

    Description

      It looks like a couple of the CTests that are ran with make test constantly fail on macOS, Linux for the 10.0 branch:

            Start 23: bulk1
      23/80 Test #23: bulk1 ............................***Failed    0.07 sec
            Start 24: performance
      24/80 Test #24: performance ......................***Failed    0.06 sec
            Start 25: basic-t
      25/80 Test #25: basic-t ..........................***Failed    0.07 sec
            Start 26: fetch
      26/80 Test #26: fetch ............................***Failed    0.07 sec
            Start 27: charset
      27/80 Test #27: charset ..........................***Failed    0.06 sec
            Start 28: logs
      28/80 Test #28: logs .............................***Failed    0.06 sec
            Start 29: cursor
      29/80 Test #29: cursor ...........................***Failed    0.07 sec
            Start 30: errors
      30/80 Test #30: errors ...........................***Failed    0.06 sec
            Start 31: view
      31/80 Test #31: view .............................***Failed    0.07 sec
            Start 32: ps
      32/80 Test #32: ps ...............................***Failed    0.07 sec
            Start 33: ps_bugs
      33/80 Test #33: ps_bugs ..........................***Failed    0.07 sec
            Start 34: sp
      34/80 Test #34: sp ...............................***Failed    0.06 sec
            Start 35: result
      35/80 Test #35: result ...........................***Failed    0.07 sec
            Start 36: connection
      36/80 Test #36: connection .......................***Failed    0.06 sec
            Start 37: misc
      37/80 Test #37: misc .............................***Failed    0.07 sec
            Start 38: ps_new
      38/80 Test #38: ps_new ...........................***Failed    0.07 sec
            Start 39: thread
      39/80 Test #39: thread ...........................***Failed    0.06 sec
            Start 40: features-10_2
      40/80 Test #40: features-10_2 ....................***Failed    0.08 sec
            Start 41: dyncol
      41/80 Test #41: dyncol ...........................***Failed    0.06 sec
            Start 42: async
      42/80 Test #42: async ............................***Failed    0.06 sec
      

      Is this a known issue? How is running make test different than ./mtr --suite=unit? Is running make test advised in any case in favor of mtr?

      Attachments

        Issue Links

          Activity

            teodor Teodor Mircea Ionita (Inactive) created issue -
            teodor Teodor Mircea Ionita (Inactive) made changes -
            Field Original Value New Value
            Affects Version/s 10.2.0 [ 20700 ]
            Affects Version/s 10.0 [ 16000 ]

            It looks like the failing tests were introduced in 10.2.

            teodor Teodor Mircea Ionita (Inactive) added a comment - It looks like the failing tests were introduced in 10.2.

            ./mtr --suite=unit starts mysqld that unit tests are using. When you run them standalone, they fail as they cannot find the server.

            serg Sergei Golubchik added a comment - ./mtr --suite=unit starts mysqld that unit tests are using. When you run them standalone, they fail as they cannot find the server.

            In that case, wouldn't it be better if make test would run MTR in the first place? Or at least print a useful message?

            teodor Teodor Mircea Ionita (Inactive) added a comment - - edited In that case, wouldn't it be better if make test would run MTR in the first place? Or at least print a useful message?

            Absolutely. That would be ideal.

            serg Sergei Golubchik added a comment - Absolutely. That would be ideal.
            cvicentiu Vicențiu Ciorbaru made changes -
            Assignee Vicentiu Ciorbaru [ cvicentiu ]
            cvicentiu Vicențiu Ciorbaru made changes -
            cvicentiu Vicențiu Ciorbaru made changes -

            We should properly fix this, just to make life easier for certain distributions.

            There is a problem with overriding `make test` command in cmake. CMake will issue a warning when this is done by creating a new target. There should be a "proper" way to get it working.

            cvicentiu Vicențiu Ciorbaru added a comment - We should properly fix this, just to make life easier for certain distributions. There is a problem with overriding `make test` command in cmake. CMake will issue a warning when this is done by creating a new target. There should be a "proper" way to get it working.
            cvicentiu Vicențiu Ciorbaru made changes -
            teodor Teodor Mircea Ionita (Inactive) made changes -
            teodor Teodor Mircea Ionita (Inactive) made changes -

            Managed to come up with a solution after quite a bit of headache. See PR at https://github.com/MariaDB/server/pull/746.

            It is based on the solution explained here https://stackoverflow.com/questions/31252228/cmake-and-ctests-default-test-command-skips-a-specially-named-test

            teodor Teodor Mircea Ionita (Inactive) added a comment - Managed to come up with a solution after quite a bit of headache. See PR at https://github.com/MariaDB/server/pull/746 . It is based on the solution explained here https://stackoverflow.com/questions/31252228/cmake-and-ctests-default-test-command-skips-a-specially-named-test

            Yes, I've seen it. Very nice trick. Looks like the best we could do...

            serg Sergei Golubchik added a comment - Yes, I've seen it. Very nice trick. Looks like the best we could do...
            serg Sergei Golubchik made changes -
            Fix Version/s 10.2 [ 14601 ]
            serg Sergei Golubchik made changes -
            Assignee Vicentiu Ciorbaru [ cvicentiu ] Sergei Golubchik [ serg ]
            serg Sergei Golubchik made changes -
            Priority Minor [ 4 ] Major [ 3 ]
            teodor Teodor Mircea Ionita (Inactive) made changes -
            issue.field.resolutiondate 2018-07-02 08:34:52.0 2018-07-02 08:34:52.956
            teodor Teodor Mircea Ionita (Inactive) made changes -
            Fix Version/s 5.5.62 [ 22915 ]
            Fix Version/s 10.2 [ 14601 ]
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Closed [ 6 ]
            teodor Teodor Mircea Ionita (Inactive) made changes -
            Assignee Sergei Golubchik [ serg ] Teodor Mircea Ionita [ teodor ]
            Resolution Fixed [ 1 ]
            Status Closed [ 6 ] Stalled [ 10000 ]

            Closing this since, as discussed, the fix in PR#746 was merged and reverted due to insufficient verbosity while running for a long time and no other solution is likely possible at the present moment with cmake/ctest 3.11.

            teodor Teodor Mircea Ionita (Inactive) added a comment - Closing this since, as discussed, the fix in PR#746 was merged and reverted due to insufficient verbosity while running for a long time and no other solution is likely possible at the present moment with cmake/ctest 3.11.
            teodor Teodor Mircea Ionita (Inactive) made changes -
            Resolution Won't Fix [ 2 ]
            Status Stalled [ 10000 ] Closed [ 6 ]
            teodor Teodor Mircea Ionita (Inactive) made changes -
            Comment [ Closing this since, as discussed, the fix in [PR#746|https://github.com/MariaDB/server/pull/746] was merged and reverted due to insufficient verbosity while running for a long time and no other solution is likely possible at the present moment with cmake/ctest 3.11. ]
            serg Sergei Golubchik made changes -
            Workflow MariaDB v3 [ 86890 ] MariaDB v4 [ 154294 ]

            People

              teodor Teodor Mircea Ionita (Inactive)
              teodor Teodor Mircea Ionita (Inactive)
              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.