Bug#1074648: libdbd-mariadb-perl: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

[Lucas Nussbaum]

Source: libdbd-mariadb-perl
Version: 1.22-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> /<<PKGBUILDDIR>>/debian/tests/pkg-perl/smoke-setup: 21: /usr/bin/mysqladmin: not found
> /<<PKGBUILDDIR>>/debian/tests/pkg-perl/smoke-setup: 21: /usr/bin/mysqladmin: not found
> /<<PKGBUILDDIR>>/debian/tests/pkg-perl/smoke-setup: 21: /usr/bin/mysqladmin: not found
> /<<PKGBUILDDIR>>/debian/tests/pkg-perl/smoke-setup: 21: /usr/bin/mysqladmin: not found
> /<<PKGBUILDDIR>>/debian/tests/pkg-perl/smoke-setup: 21: /usr/bin/mysqladmin: not found
> /<<PKGBUILDDIR>>/debian/tests/pkg-perl/smoke-setup: 21: /usr/bin/mysqladmin: not found
> /<<PKGBUILDDIR>>/debian/tests/pkg-perl/smoke-setup: 21: /usr/bin/mysqladmin: not found
> /<<PKGBUILDDIR>>/debian/tests/pkg-perl/smoke-setup: 21: /usr/bin/mysqladmin: not found
> /<<PKGBUILDDIR>>/debian/tests/pkg-perl/smoke-setup: 21: /usr/bin/mysqladmin: not found
> /<<PKGBUILDDIR>>/debian/tests/pkg-perl/smoke-setup: 21: /usr/bin/mysqladmin: not found
> skipping test, mariadb/mysql server could not be contacted after 30 seconds
> make[1]: *** [debian/rules:31: override_dh_auto_test] Error 1
> make[1]: Leaving directory '/<<PKGBUILDDIR>>'
> make: *** [debian/rules:23: binary] Error 2
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2024/07/02/libdbd-mariadb-perl_1.22-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.