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

MTR should report at least last test that was executed in case of shutdown and not-completed

Details

    Description

      As stated in description MTR should report in that cases the last test that was executed.
      That information can be extracted from CURRENT_TEST that is written in log file.
      In attachment is suggested patch, that works in case tests are not completed.
      Patch - bb-10.6-anel-MDEV-25506.

      However, in case of shutdown on Windows environment, result is visible in verbose mode mtr --verbose. Without the flag verbose I couldn't obtain the same result.
      Note: the patch contains some information for debugging purposes only and to show you here i description. I will remove them after review. Does it mean that mtr_report_test doesn't work in Windows?
      Invoke mtr with test case encryption.innodb-bad-key-change4 on branch bb-10.6-anel-MDEV-25506
      Results in Windows without the patch and with the patch without verbose flag - test not visible:

      ==============================================================================
      		 
      TEST                                      RESULT   TIME (ms) or COMMENT
      		 
      --------------------------------------------------------------------------
      		 
      worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 16000..16019
      		 
      worker[1] mysql-test-run: WARNING: Process [mysqld.1 - pid: 17188, winpid: 17188, exit: 512] died after mysql-test-run waited 0.42 seconds for D:/server/bld_10.6/mysql-test/var/run/mysqld.1.pid to be created.
      		 
      worker[1] mysql-test-run: *** ERROR: Failed to start mysqld mysqld.1 with command D:/server/bld_10.6/sql//Debug/mariadbd.exe

      Result with verbose mode - test visible

      worker[1] > mysqld_start restart:  [' --plugin-load-add=file_key_management.so', '--file-key-management', '--file-key-management-filename=D:/server/mysql-test/std_data/keys2.txt ']
      		 
      worker[1] > Started [mysqld.1 - pid: 17452, winpid: 17452]
      		 
      worker[1] mysql-test-run: WARNING: Process [mysqld.1 - pid: 17452, winpid: 17452, exit: 512] died after mysql-test-run waited 0.43 seconds for D:/server/bld_10.6/mysql-test/var/run/mysqld.1.pid to be created.
      		 
      worker[1] Ovdje sam
      		 
      worker[1] D:/server/bld_10.6/mysql-test/var/log/current_test
      		 
      worker[1] Ovdje sam
      		 
      worker[1] encryption.innodb-bad-key-change4
      		 
      safe_process[8548]: parent_pid: 16212
      		 
      safe_process[8548]: Started child 9996
      		 
       worker[1] [ fail ]
      		 
              Test ended at 2021-06-03 13:45:41
      		 
      worker[1]
      		 
      D:/server/bld_10.6/mysql-test/var/log/current_test
      		 
      worker[1] mysql-test-run: *** ERROR: Failed to start mysqld mysqld.1 with command D:/server/bld_10.6/sql//Debug/mariadbd.exe

      Note that this line - mtr_report_test is not executed and I don't see how to fix this on Windows.
      Any idea wlad ?

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-30186 Use of uninitialized value $test_name in substitution

          • Major - Major loss of function.
          • Closed

          Activity

            People

              anel Anel Husakovic
              anel Anel Husakovic
              Votes:
              0 Vote for this issue
              Watchers:
              4 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.