[MDEV-31349] test maria.maria-purge failed on 'aria_log.00000002 not found' Created: 2023-05-26 Updated: 2023-10-09 Resolved: 2023-10-09 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Tests |
| Affects Version/s: | 10.11.3, 10.9, 10.10, 10.11, 11.0 |
| Fix Version/s: | 10.5.23, 10.6.16, 10.9.8, 10.10.7, 10.11.6, 11.0.4, 11.1.3 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Otto Kekäläinen | Assignee: | Michael Widenius |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
After uploading MariaDB 10.11.3 to Launchpad builders several of them failed on test maria.maria-purge:
Examples from amd64 and arm64 builds: |
| Comments |
| Comment by Alice Sherepa [ 2023-06-23 ] | |||||||||||||||||||||
|
| |||||||||||||||||||||
| Comment by Otto Kekäläinen [ 2023-10-05 ] | |||||||||||||||||||||
|
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:
Examples:
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:
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. | |||||||||||||||||||||
| Comment by Otto Kekäläinen [ 2023-10-05 ] | |||||||||||||||||||||
|
I also saw this on official Debian CI, see log at https://ci.debian.net/data/autopkgtest/unstable/amd64/m/mariadb/38571769/log.gz. | |||||||||||||||||||||
| Comment by Otto Kekäläinen [ 2023-10-05 ] | |||||||||||||||||||||
|
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. | |||||||||||||||||||||
| Comment by Otto Kekäläinen [ 2023-10-07 ] | |||||||||||||||||||||
|
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:
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. | |||||||||||||||||||||
| Comment by Michael Widenius [ 2023-10-08 ] | |||||||||||||||||||||
|
The problem was that maria_empty_logs.inc deleted aria log files before The test failed if there was a lot of old aria log files from previous tests. | |||||||||||||||||||||
| Comment by Otto Kekäläinen [ 2023-10-09 ] | |||||||||||||||||||||
|
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. |