Dear loong64 porters,As I assume you're aware, since some time we have loong64 support on ci.debian.net, the infrastructure where we run autopkgtests for migration. I started to notice that packages that test depend on mariadb-server or mysql-server tmpfail after 50 minutes due to timeout. When I looked into some of the logs, it happens while installing the test dependencies and in all cases, it's either mariadb-server or mysql-server that's being installed when the timeout happens.
E.g. https://ci.debian.net/packages/m/mysql-8.0/unstable/loong64/ https://ci.debian.net/packages/m/mariadb/unstable/loong64/ https://ci.debian.net/packages/c/cacti/unstable/loong64/ https://ci.debian.net/packages/p/python-testing.mysqld/unstable/loong64/ https://ci.debian.net/packages/r/ruby-mysql2/unstable/loong64/ https://ci.debian.net/packages/m/mysql-connector-c++/unstable/loong64/ With MariaDB: https://ci.debian.net/data/autopkgtest/unstable/loong64/m/mariadb/53126838/log.gz 111s Setting up mariadb-client (1:11.4.3-1) ... 111s Setting up mariadb-server (1:11.4.3-1) ... 3104s autopkgtest [22:59:53]: ERROR: testbed failure: timed out With MySQL: https://ci.debian.net/data/autopkgtest/unstable/loong64/m/mysql-8.0/53128027/log.gz 100s Setting up mysql-server-core-8.0 (8.0.39-1) ... 100s Setting up mysql-server-8.0 (8.0.39-1) ...101s update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode
101s Renaming removed key_buffer and myisam-recover options (if present) 108s mysqld will log errors to /var/log/mysql/error.log 109s mysqld is running as pid 1244109s /var/lib/dpkg/info/mysql-server-8.0.postinst: line 56: kill: (1244) - Operation not permitted
3098s autopkgtest [11:55:05]: ERROR: testbed failure: timed out It might be worth figuring out why this happens on loong64. Paul PS: I noticed bug 1077229 exists, but that seems to have gone away now. https://bugs.debian.org/1077229
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature