Source: puma Version: 4.3.1-1 Severity: serious Tags: experimental Usertags: ftbfs-experimental
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 The build of puma in experimental failed for several architectures. On amd64 it gets stuck for no obvious reason and must be killed forcefully after some time. The issue is also reproducible locally and on salsa.d.o, although it did not appear during the team sprint in Paris. Then the tests went fine and fast. The situation does not improve with the latest release 4.3.2. Disabling test_integration_cluster.rb doesn't help either, so it is not related to these tests. I need help to examine the cause. JFTR: For some other architestures there are other isses. Regards, Daniel - -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled - -- no debconf information -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAl5Y8DwACgkQS80FZ8KW 0F3K9A/8DwzmXLk6L0WymvxGFqO2HAV4Dz2QGkhmMPDB9b4dRq9vPK2n08+Y+nhi hxRbsR8Vt6nhr4a0LWVqMLZm2lxnVB5KwRMTl38/9E4CSw/PnU1HIl13YwTOeSCT zJZ/3QuFSNUr4Ea+FTgf2Bchv1lphQddflL18kqV+GW86ptFD96ABQ27QpULmPzn xJxNLc2g3qQUUxyxevg++ajs4Xc54vdu22wU0xqlkA8yTtpIHpkkDgRS86IrObDi WmDq5aatxgaEQSKqSLcVpKk3ayVXZTYVMpA1Qz0I1qGkIqL4VgdF2ghE/8tUUTLQ UOMre/zPSNnOl47LT88a4FvzycL1zoUTwaqsIyYEPhfyqHjEqqq/5BgUbD230frJ 1J7sseWGogVO/fG8YJhxU2o/pg7Pl/BAXvVlpcLU6dMnBPt765Mq71gcRCoyFP0Z KciKO58CwWCiOSu+pBN5YwUtdFvnxpXh1CammKxgGjlnUbFaIxHfJeEUviE8COeD qK2PSDObOKGWW0bjcNskfExMum09sYR6r20HuYvHVNgTf2Qp9vlVUL8AEsnfNV1D K6v6xihE2c7ndZtj0G0tzqWve2fnNQsrtF+2Ec0maOHEDqFyNC3Jxtv5f3scSZeF Un2T4H3IKq0bkBbHmFd8RU6mILiD1Kf9Nr0VcTbtOgcA6VLEzXQ= =P92Z -----END PGP SIGNATURE-----
