Anel Husakovic added a comment - 2021-03-29 06:02 It works for me: [0/1] Re-running CMake... CMake Deprecation Warning at CMakeLists.txt:17 (CMAKE_MINIMUM_REQUIRED): Compatibility with CMake < 2.8.12 will be removed from a future version of CMake.   Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions.     -- Running cmake version 3.20.0-rc4 -- MariaDB 10.5.9 -- Updating submodules CMake Deprecation Warning at wsrep-lib/CMakeLists.txt:5 (cmake_minimum_required): Compatibility with CMake < 2.8.12 will be removed from a future version of CMake.   Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions.     -- Wsrep-lib version: 1.0.0 == Configuring MariaDB Connector/C CMake Deprecation Warning at libmariadb/CMakeLists.txt:5 (CMAKE_MINIMUM_REQUIRED): Compatibility with CMake < 2.8.12 will be removed from a future version of CMake.   Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions.     -- MariaDB Connector/c configuration: -- Static PLUGINS mysql_native_password;mysql_old_password;pvio_socket -- Dynamic PLUGINS dialog;client_ed25519;caching_sha2_password;auth_gssapi_client;mysql_clear_password -- CPack generation: TGZ -- SSL support: GNUTLS Libs: /usr/lib/x86_64-linux-gnu/libgnutls.so -- Zlib support: ON -- Installation layout: DEFAULT -- Include files will be installed in include/mysql -- Libraries will be installed in lib -- Binaries will be installed in bin -- Documentation included from -- Required: dl;m;pthread -- MariaDB Connector/C 3.1.12 CMake Deprecation Warning at storage/mroonga/CMakeLists.txt:20 (cmake_minimum_required): Compatibility with CMake < 2.8.12 will be removed from a future version of CMake.   Update the VERSION argument <min> value or use a ...<max> suffix to tell CMake that the project does not need compatibility with older versions.     -- Performance Schema is required by TokuDB -- Configuring done -- Generating done -- Build files have been written to: /home/anel/mariadb/builds/10.5 [1641/1641] Linking CXX executable libmysqld/examples/mariadb-test-embedded Logging: /home/anel/mariadb/10.5/mysql-test/mysql-test-run.pl main.upgrade_MDEV-19650 vardir: /home/anel/mariadb/builds/10.5/mysql-test/var Checking leftover processes... Removing old var directory... Creating var directory '/home/anel/mariadb/builds/10.5/mysql-test/var'... Checking supported features... MariaDB Version 10.5.9-MariaDB-debug - SSL connections supported - binaries are debug compiled - binaries built with wsrep patch Collecting tests... Installing system database...   ==============================================================================   TEST RESULT TIME (ms) or COMMENT --------------------------------------------------------------------------   worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 16000..16019 main.upgrade_MDEV-19650 [ pass ] 424 -------------------------------------------------------------------------- The servers were restarted 0 times Spent 0.424 of 4 seconds executing testcases   Completed: All 1 tests were successful. And is not failed in buildbot: https://buildbot.mariadb.org/#/grid?branch=10.5

Thomas Deutschmann added a comment - 2021-03-29 15:18 When I run this test manually it passes, too. But when I run the entire test suite with MTR_PARALLEL=32 on a powerful server it fails. So maybe load/order related?

Anel Husakovic added a comment - 2021-03-29 15:23 Maybe. I don't know we are using such parallelism, danblack ?

Daniel Black added a comment - 2022-06-06 03:42 Its more likely to be the order that the tests occurred for this worker. I've checked our recent records of builtbot runs and cannot see an error of this form. If you come across it again can you look at the series of tests that the wXXX worker executed the test in and record those.

Elena Stepanova added a comment - 2022-07-04 14:02 To re-phrase the above, please provide the full stdout from the failing MTR run (either a copy-paste from the console or var/log/stdout.log).