El 17/11/24 a las 21:37, Johannes Schauer Marin Rodrigues escribió:
Another thing you could try is to see if maybe this only happens with unstable chroot but not with bookworm chroots. That would point to something in unstable having changed (apt?).
Yes, it's apparently some build-dependency. See for example my build history for node-dagre-d3-renderer in trixie using machines with 2 CPUs: Status: successful node-dagre-d3-renderer_0.6.4+dfsg-7_amd64-20240830T101510.571Z Status: successful node-dagre-d3-renderer_0.6.4+dfsg-7_amd64-20240924T141820.007Z Status: successful node-dagre-d3-renderer_0.6.4+dfsg-7_amd64-20241006T140553.593Z Status: successful node-dagre-d3-renderer_0.6.4+dfsg-7_amd64-20241030T060505.673Z Status: failed node-dagre-d3-renderer_0.6.4+dfsg-7_amd64-20241117T010321.514Z Status: failed node-dagre-d3-renderer_0.6.4+dfsg-7_amd64-20241117T091551.769Z Status: failed node-dagre-d3-renderer_0.6.4+dfsg-7_amd64-20241117T091924.749Z Status: failed node-dagre-d3-renderer_0.6.4+dfsg-7_amd64-20241117T092942.053Z Status: failed node-dagre-d3-renderer_0.6.4+dfsg-7_amd64-20241117T102025.563Z The failed build logs have this at the end: E: Build killed with signal TERM after 60 minutes of inactivity (probably related with the process which was not killed properly) Simple question: If I decide to use debbisect for this, how would the timeout be handled? Does mmdebstrap have a timeout like sbuild? Thanks.
