El 18/8/23 a las 11:33, Simon McVittie escribió:
Does your archive rebuild infrastructure build other things in parallel on the same machine,
Usually yes, however...
or any other factor like that which could make it more likely to get stuck / take a long time than a production buildd?
it also happens for me on Hetzner instances when they have only one CPU. In fact, the failure rate there is around 50%, see my build history: Status: successful mutter_42.2-1_amd64-20220602T145801.175Z Status: successful mutter_42.2-1_amd64-20220602T145853.866Z Status: successful mutter_42.3-2_amd64-20220722T000038.817Z Status: failed mutter_42.4-2_amd64-20220822T140107.057Z Status: failed mutter_43.0-2_amd64-20221001T033721.484Z Status: successful mutter_43.0-2_amd64-20221026T224643.425Z Status: failed mutter_43.0-2_amd64-20221026T225023.605Z Status: successful mutter_43.0-2_amd64-20221026T225735.334Z Status: failed mutter_43.0-2_amd64-20221026T230205.166Z Status: failed mutter_43.0-2_amd64-20221026T230429.710Z Status: successful mutter_43.0-2_amd64-20221026T230445.865Z Status: successful mutter_43.0-2_amd64-20221026T230950.351Z Status: failed mutter_43.0-2_amd64-20221026T231613.500Z Status: successful mutter_43.0-2_amd64-20221026T231928.067Z Status: failed mutter_43.0-2_amd64-20221026T232232.536Z Status: successful mutter_43.0-3_amd64-20221027T030436.778Z Status: failed mutter_43.1-1_amd64-20221110T204455.431Z Status: failed mutter_43.1-2_amd64-20221118T165401.759Z Status: failed mutter_43.2-4_amd64-20221228T163225.025Z Status: successful mutter_43.2-5_amd64-20230126T051730.091Z Status: successful mutter_43.2-5_amd64-20230126T123916.064Z Status: successful mutter_43.2-5_amd64-20230126T124415.417Z Status: failed mutter_43.2-5_amd64-20230126T124912.497Z Status: successful mutter_43.2-5_amd64-20230126T125745.097Z Status: failed mutter_43.2-5_amd64-20230126T130505.181Z Status: successful mutter_43.2-5_amd64-20230126T130313.890Z Status: failed mutter_43.2-5_amd64-20230126T131615.214Z Status: successful mutter_43.2-5_amd64-20230126T132338.826Z Status: successful mutter_43.2-5_amd64-20230126T132314.189Z Status: successful mutter_43.2-5_amd64-20230126T133201.921Z Status: failed mutter_43.2-5_amd64-20230126T155759.258Z Status: failed mutter_43.2-5_amd64-20230126T155924.752Z Status: failed mutter_43.2-6_amd64-20230201T052934.943Z Status: failed mutter_43.3-3_amd64-20230301T063919.406Z Status: failed mutter_43.3-4_amd64-20230305T060548.547Z Status: failed mutter_43.3-5_amd64-20230317T110143.226Z Status: successful mutter_43.4-1_amd64-20230418T054643.208Z Status: failed mutter_43.4-2_amd64-20230429T050402.816Z Status: failed mutter_43.6-1~deb12u1_amd64-20230722T122053.236Z Status: failed mutter_43.6-1~deb12u1_amd64-20230722T123559.302Z Status: failed mutter_43.6-1~deb12u1_amd64-20230722T123656.554Z Status: failed mutter_43.6-1~deb12u1_amd64-20230722T123717.438Z Status: failed mutter_43.6-1~deb12u1_amd64-20230722T124448.583Z (Note: That was for bookworm, but it has not improved at all in trixie) So, I suggest that you first try GRUB_CMDLINE_LINUX="nr_cpus=1" in /etc/default/grub, just as a way to increase the likelihood of failure. Then, if that's not enough to get at least random failures, please contact me privately, as I will gladly provide ssh access for you to a machine where this happens. Thanks.
