[DRE-maint] Bug#978251: ruby-mysql2: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

[Lucas Nussbaum]

Source: ruby-mysql2
Version: 0.5.3-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

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

Relevant part (hopefully):
> + cleanup
> + /usr/bin/mysqladmin --user=root --socket=/tmp/tmp.g8cXe135ad/mysql.sock shutdown
> 2020-12-26 15:17:41 9 [Warning] Access denied for user 'root'@'localhost'
> /usr/bin/mysqladmin: connect to server at 'localhost' failed
> error: 'Access denied for user 'root'@'localhost''
> rake aborted!
> Command failed with status (1): [./debian/start_mysqld_and_run.sh ruby2.7 -...]
> /<<PKGBUILDDIR>>/debian/ruby-tests.rake:8:in `block in <top (required)>'
> /usr/share/rubygems-integration/all/gems/rake-13.0.1/exe/rake:27:in `<top (required)>'
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby2.7" failed. Exiting.
> dh_auto_install: error: dh_ruby --install /<<PKGBUILDDIR>>/debian/ruby-mysql2 returned exit code 1
> make: *** [debian/rules:6: binary] Error 25
> dpkg-buildpackage: error: fakeroot 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/2020/12/26/ruby-mysql2_0.5.3-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 marking 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 me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.