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

mtr appears to hang at start on macOS 13.6.3

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 11.4
    • 11.4.2
    • Server, Tests
    • None

    Description

      When running mtr on macOS with source built from current (as of this ticket) 11.4, it hangs and doesn't ever progress to a test.

      Running mtr with arguments: --verbose --verbose --verbose --force --max-test-fail=0 --parallel=auto --suite=main
      it gets stuck at:

      worker[01] > Running test: main.connect
      		 
      worker[01] > Setting timezone: DEFAULT
      		 
      worker[01] Stopping  [mysqld.1 - pid: 3803, winpid: 3803]
      		 
      ### safe_path: /Users/dgosselin/3/server/mariadb-build/mysql-test/lib/My/SafeProcess/my_safe_process --verbose -- /Users/dgosselin/3/server/mariadb-build/client//mariadb-admin --no-defaults --character-sets-dir=/Users/dgosselin/3/server/sql/share/charsets --user=root --password= --port=16000 --host=localhost --connect_timeout=20 --protocol=tcp shutdown

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. MDEV-33075 Sending TERM to mariadb no longer gracefully terminates the process

          • Major - Major loss of function.
          • Closed
          relates to

          Task - A task that needs to be done. MDEV-34185 macOS Build & Test

          • Major - Major loss of function.
          • Open

          Activity

            People

              Gosselin Dave Gosselin
              Gosselin Dave Gosselin
              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.