Details
Major Description
Reproduce
1. Compile with -DPLUGIN_MROONGA=NO
2.
mtr --suite=mroonga
|
Result
Use of uninitialized value $test_name in substitution (s///) at /home/midenok/src/mariadb/10.6/src/mysql-test/mariadb-test-run.pl line 519.
|
Use of uninitialized value $test_name in scalar chomp at /home/midenok/src/mariadb/10.6/src/mysql-test/mariadb-test-run.pl line 520.
|
Use of uninitialized value in concatenation (.) or string at lib/My/Test.pm line 54.
|
[ fail ]
|
Attachments
Issue Links
- is caused by
-
MDEV-25857 MTR should report at least last test that was executed in case of shutdown and not-completed
-
- Closed
-
Activity
Patch of MDEV-25857 is pushed to 10.6 first
$ git tag --contains 29e8c154172bd6b9dccd9757fddace93be6ad194|grep 10.3 |
So by testing above on 10.3 we get:
$ ./mysql-test/mtr --suite=mroonga |
Logging: /home/anel/GitHub/mariadb/server/src/10.3/mysql-test/mysql-test-run.pl --suite=mroonga |
VS config:
|
vardir: /home/anel/GitHub/mariadb/server/build/10.3/mysql-test/var |
Removing old var directory...
|
- WARNING: Using the 'mysql-test/var' symlink |
The destination for symlink /home/anel/GitHub/mariadb/server/build/10.3/mysql-test/var does not exist; Removing it and creating a new var directory |
Creating var directory '/home/anel/GitHub/mariadb/server/build/10.3/mysql-test/var'... |
Checking supported features...
|
MariaDB Version 10.3.38-MariaDB-debug
|
- SSL connections supported
|
- binaries are debug compiled
|
- binaries built with wsrep patch
|
Using suites: mroonga
|
Collecting tests...
|
Installing system database...
|
|
|
==============================================================================
|
|
|
TEST RESULT TIME (ms) or COMMENT
|
--------------------------------------------------------------------------
|
|
|
worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 16000..16019
|
mysql-test-run: *** ERROR: Test suite aborted |
I don't see for example on connect same error, it works.
midenok can you please review my PR 2387and should we target for 10.6+ ?
anel Can you take test name from the running state, not by parsing the logs?