Alice Sherepa added a comment - 2023-06-23 19:05 10.9 e1a631fecc364ce1268b13a81 alice@:~/git/10.10/mysql-test$ ./mtr maria.maria-big maria.maria-purge Logging: ./mtr maria.maria-big maria.maria-purge   ==============================================================================   TEST RESULT TIME (ms) or COMMENT --------------------------------------------------------------------------   worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 16000..16019 maria.maria-big [ pass ] 8664 maria.maria-purge [ fail ] Found warnings/errors in server log file! Test ended at 2023-06-23 21:02:01 line 2023-06-23 21:01:51 0 [ERROR] mariadbd: File '/10.10/mysql-test/var/mysqld.1/data/aria_log.00000002' not found (Errcode: 2 "No such file or directory") 2023-06-23 21:01:51 0 [ERROR] mariadbd: Aria engine: log purging failed ^ Found warnings in /10.10/mysql-test/var/log/mysqld.1.err ok -------------------------------------------------------------------------- The servers were restarted 0 times Spent 8.664 of 26 seconds executing testcases

Otto Kekäläinen added a comment - 2023-10-05 04:34 I am seeing this same error now on Salsa CI with 10.11.5 builds, and also when I run build+MTR inside a Docker container on my own laptop: maria.maria-purge w1 [ fail ] Found warnings/errors in server log file! Test ended at 2023-10-05 02:57:14 line 2023-10-05 2:57:11 0 [ERROR] mariadbd: File '/builds/otto/mariadb-server/debian/output/source_dir/builddir/mysql-test/var/1/mysqld.1/data/aria_log.00000002' not found (Errcode: 2 "No such file or directory") 2023-10-05 2:57:11 0 [ERROR] mariadbd: Aria engine: log purging failed ^ Found warnings in /builds/otto/mariadb-server/debian/output/source_dir/builddir/mysql-test/var/1/log/mysqld.1.err Examples: https://salsa.debian.org/otto/mariadb-server/-/jobs/4770929/raw https://salsa.debian.org/otto/mariadb-server/-/jobs/4770925/raw This is not a sporadic failure but repeats ever time in the build+MTR situation. However, if I run MTR outside of the built sources this test passes, example from https://salsa.debian.org/otto/mariadb-server/-/jobs/4767530/raw: maria.maria-purge w2 [ pass ] 11707 Thus there is something weird going on specifically when the test is run with freshly built binaries in the source code directory which does not occur when running test in standalone mode.

Otto Kekäläinen added a comment - 2023-10-05 05:29 I also saw this on official Debian CI, see log at https://ci.debian.net/data/autopkgtest/unstable/amd64/m/mariadb/38571769/log.gz .

Otto Kekäläinen added a comment - 2023-10-05 07:14 I can reproduce this also at https://launchpad.net/~mysql-ubuntu/+archive/ubuntu/mariadb-10.11/+builds?build_text=&build_state=all on basically all architectures.

Otto Kekäläinen added a comment - 2023-10-07 21:50 - edited I can confirm that when MTR runs outside of the source directory as pure test system (e.g. installed via mariadb-test package as described in https://optimizedbyotto.com/post/grokking-mariadb-test-run-mtr/ or at https://ci.debian.net/packages/m/mariadb/ ) this test does pass: maria.maria-purge w1 [ pass ] 4795 eg. https://ci.debian.net/data/autopkgtest/testing/ppc64el/m/mariadb/38598140/log.gz , https://ci.debian.net/data/autopkgtest/testing/i386/m/mariadb/38691874/log.gz , https://ci.debian.net/data/autopkgtest/testing/s390x/m/mariadb/38691392/log.gz However, when MTR runs in source tree directory after a build the test always fails on all platforms I tested.

Michael Widenius added a comment - 2023-10-08 14:56 The problem was that maria_empty_logs.inc deleted aria log files before the server was properly shutdown. Fixed by waiting for pid file to disappear before starting to delete log files. The test failed if there was a lot of old aria log files from previous tests.

Otto Kekäläinen added a comment - 2023-10-09 18:33 I confirm https://github.com/MariaDB/server/commit/185591c1c0dfd16bc6f74999a23d5aa5d7cfb12b fixed this test failure - it is no longer visible on any of my test builds on Launchpad.