Uploaded image for project: 'Percona Toolkit'
  1. Percona Toolkit
  2. PT-2161

Fix tests for pt-slave-restart

Details

    • Improvement
    • Status: Done
    • Medium
    • Resolution: Fixed
    • 3.5.0
    • 3.5.2
    • None
    • None
    • Yes
    • Yes
    • 2

    Description

      How to Repeat

      Results are for PS-8.0.30

      $ prove -vw --trap --timer t/pt-slave-restart/
      [18:10:50] t/pt-slave-restart/gtid.t ...................... # Restarting the sandbox
      DBD::mysql::db do failed: LOAD DATA LOCAL INFILE file request rejected due to restrictions on access. [for Statement "LOAD DATA LOCAL INFILE '/tmp/load_data_test.2671988' INTO TABLE percona_test.load_data"] at ../util/check-load-data line 48.
      # MySQL test server on port 12349 does not exist.
      # MySQL test server on port 12348 does not exist.
      # Stopping MySQL test server on port 12347... OK (4s)
      # Stopping MySQL test server on port 12346... OK (12s)
      # Stopping MySQL test server on port 12345... OK (12s)
      # MySQL test server on port 2903 does not exist.
      # MySQL test server on port 2902 does not exist.
      # MySQL test server on port 2901 does not exist.
      # MySQL test server on port 2900 does not exist.
      # Percona Toolkit test environment stopped.
      # master 12345
      # Creating default databases ...
      # Starting MySQL test server on port 12345... return 0
      # OK (2s)
      # Creating default databases ...
      # Starting MySQL test server on port 12346... return 0
      # OK (3s)
      # Creating default databases ...
      # Starting MySQL test server on port 12347... return 0
      # OK (3s)
      # LOAD DATA LOCAL INFILE is disabled
      # Waiting for replication to finish... OK
      # Percona Toolkit test environment started with MySQL v8.0.
      # Sandbox restarted
      
      not ok 1 - slave: Replication broke
      
      #   Failed test 'slave: Replication broke'
      #   at t/pt-slave-restart/gtid.t line 112.
      #                   'Coordinator stopped because there were error(s) in the worker(s). The most recent failure being: Worker 1 failed executing transaction '5fcd75ca-8dd4-11ed-9d8c-98af65266957:22' at master log mysql-bin.000002, end_log_pos 8231. See error log and/or performance_schema.replication_applier_status_by_worker table for more details about this failure or others, if any.'
      #     doesn't match '(?^:Table 'test.t' doesn't exist')'
      not ok 2 - Event is skipped
      Bailout called.  Further testing stopped:  Replication is broken
      Bail out!  Replication is broken
      
      #   Failed test 'Event is skipped'
      #   at t/pt-slave-restart/gtid.t line 123.
      #                   '1146'
      #     doesn't match '(?^:^0$)'
      FAILED--Further testing stopped: Replication is broken
      

      Suggested Fix

      Identify which tests fail, because badly written and which show real issues with code, fix either tests or code.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              sveta.smirnova Sveta Smirnova
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Smart Checklist