Source: ruby-remcached Version: 0.4.1-3 Severity: important Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0
Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-remcached was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > No examples found. > > > Finished in 0.00005 seconds (files took 0.17408 seconds to load) > 0 examples, 0 failures, 3 errors occurred outside of examples > > rake aborted! > Command failed with status (1): [./debian/start_memcached_and_run.sh > ruby3....] > /<<PKGBUILDDIR>>/debian/ruby-tests.rake:5:in `block in <top (required)>' > Tasks: TOP => default > (See full trace by running task with --trace) > ERROR: Test "ruby3.0" failed. Exiting. > dh_auto_install: error: dh_ruby --install > /<<PKGBUILDDIR>>/debian/ruby-remcached returned exit code 1 > make: *** [debian/rules:15: 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 tests for ruby3.0 failed because eventmachine was not rebuilt for ruby3.0 yet, but the dpkg-buildpackage process stayed stuck, because the memcached that is started for the tests was never really killed. I could easily reproduce this locally. The full build log is available at https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-remcached/ruby-remcached_0.4.1-3+rebuild1633393197_amd64.build.txt
signature.asc
Description: PGP signature
